donniewest / unissist Goto Github PK

im new to this. what's the best way to just select objects i want to persist?

Unissist already allows to modify the state when saving it through the map option.
In some cases it's usefull to also be able to modify the state while loading it.

Allowing the migration function to return a promise would allow for different use cases.
For example to only import() (or otherwise load code) for migrations from the stores version.
This is usefull when you had lots of breaking changes in the store layout, but don't wan't to ship all migration code in the inital bundle.

To allow for showing user message the store could implement a migrating flag which is by default false.

To not further delay the store hydration, a check if the returned value is a promise could be made instead of always delaying the execution by a tick.

Edit: if you like the idea I could provide a PR within the next few days.

Is there any way to exclude some states from the cache?

First of all - freaking awesome library.

// store state now includes a hydrated that tells you whether or not the state has been rehydrated from the store

Could you please elaborate what hydrated does and perhaps add a few lines of example code

Currently I have a separate store file that looks like this:

import createStore from 'unistore';
import persistStore from 'unissist';
import indexedDBAdapter from 'unissist/integrations/indexdbAdapter';
const initialState = {
    //data
};

const store = createStore(initialState);
const adapter = indexedDBAdapter();

const config = {
    debounceTime: 100,
    map: state => (
        {
            //data
        }   
    )
};
persistStore(store, adapter, config);

store.subscribe((state) => console.log(state));
export default store;

If I use persistStore(store, adapter) then it will refresh correctly, however using the map, it maps the new store it creates to the adapter then hydrates store. Should this be structured a different way? I am not sure why having the config map out state causes it to default to initial state instead of hydrating. Is there something here that would cause the map to run before it rehydrates?