Restore redux state from previous sessions like a phoenix from ashes.
npm i --save redux-phoenix
Basic usage requires adding a enhancer to a redux application:
// configureStore.js import { createStore, compose } from 'redux'; import { autoRehydrate } from 'redux-phoenix'; const store = createStore(reducer, initialState, compose( applyMiddleware(...middlewares), autoRehydrate, );
And modyfing client entry point:
// index.js import React from 'react'; import { render } from 'react-dom'; import { Provider } from 'react-redux'; import store from 'configureStore'; import persistStore from 'redux-phoenix'; persistStore(store).then(store => { render( <Provider store={store}> <App /> </Provider>, document.getElementById('app') ); });
That's it. Now your redux state will be stored in localstorage.
persistStore(store, [config])
import persistStore from 'redux-phoenix'
null
means all keys will be persisted. It may be nested keys. For example: whitelist: [reducer.subfield]
persist only { reducer: { subfield: valueFromState } }
and omit all other keys.null
means no keys will be omitted. It may be nested keys and overwrite whitelisted keys.expireDate: [2, 'hours']
restore state from storage only when it is not older than 2 hours.import { autoRehydrate } from 'redux-phoenix'
import { REHYDRATE } from 'redux-phoenix'
setItem
, getItem
which returns value or a Promise resolved to value.Whitelisted keys are overwrited by blacklisted keys so is possible to omit some specific keys to not being stored.
For example given following state and configuration:
store.getState(); // { foo: { data: 'some data', errors: null, isLoading: false }, bar: { data: 'some other data } } persistStore(store, { whitelist: ['foo'], blacklist: ['foo.isLoading', 'foo.errors'], });
will persist only object { foo: { data: 'some data' } }
in storage.
There is also a possibility to transform state before saving it into storage.
Example with transformation with strings
store.getState(); // { foo: { lastValidData: 'some data', actualData: 'some data with errors' } } persistStore(store, { map: { 'foo.lastValidData': 'foo.actualData' }, });
this will persist object { foo: { lastValidData: 'some data', actualData: 'some data' } }
so that restored state will always have the last valid value in state.
Example with transformation with function
store.getState(); // { foo: { lastValidData: 'some data', actualData: 'some data with errors' } } persistStore(store, { map: { 'foo.actualData': { lastValidData: (oldKey, value, state) => ({ targetKey: 'foo.oldData', targetValue: { [oldKey]: value }, sourceValue: state.foo.lastValidData, }), }, }, });
this will persist object:
{ foo: { lastValidData: 'some data', actualData: 'some data', oldData: { 'foo.actualData': 'some data with errors' } } }
so that is possible to modify state to much complicated form.
When the throttle is defined, the state will not be saved at every action dispatched in the time set. It will take the state after the last action of this period of time. This can be useful to lower the charge of an external API.
persistStore(store, { throttle : 1000, } ); // The state will be save maximum one time / 1000 ms
You can pass migrations that will be run just before rehydrating redux store. This allows to modify the old version of state that could be persisted previously, to the new version that is used currently. Note when you want to revert the migration that might be applied previously just omit the up
method in the migration object.
const migrations = [ { name: '001-initial-migration', up: state => ({ ...state, { newField: 'newFieldValue' } }), down: state => state, }, { name: '002-missing-migration', up: state => ({ ...state, { anotherNewField: 'newValue' } }), down: state => _.omit(state, 'anotherNewField'), }, ]; persistStore(store, { migrations }); // There will be applied missing migrations from 2 passed
const migrations = [ { name: '001-initial-migration', up: state => ({ ...state, { newField: 'newFieldValue' } }), down: state => state, }, { name: '002-reverted', down: state => state, }, ]; persistStore(store, { migrations }); // There will be applied migration 001 (if not present) and reverted 002 (if present)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4