Partial initial state and usage help / docs about redux-persist-transform-filter HOT 3 OPEN

I was just looking into this for a new React Native app and after some debugging it looks like using the autoMergeLevel2 state reconciler fixes this issue for me. When using the autoMergeLevel1 state reconciler the whole reducer gets replaced as noted here https://github.com/rt2zz/redux-persist/blob/208c6b112ead87b3701dfacaae2cdbe78377775a/src/stateReconciler/autoMergeLevel1.js#L33 which causes it to blow the initial state up. autoMergeLevel2 merges it instead of only using the persisted state

from redux-persist-transform-filter.

@edy Any hints on this? This prevents from using nested keys (a.b.c) as the loaded state isn't properly merged to the existing state, rather replaces it completely.

Edit
This problem is actually caused by redux-persist only supporting (out of the box) 2 levels of auto merging. Implementing a deep merge state reconciler might be the way to go.

Related rt2zz/redux-persist#491

from redux-persist-transform-filter.

#24

from redux-persist-transform-filter.