Loading from the storage does not overwrite initial state completely

Hi, it seems that loading from the storage does not overwrite the initial state completely, and that looks like a bug for me. ( If it’s not, please tell me how I can work with it productively. 😃 )

An example: Let’s say, this is my initial state:

state = {
  ...
  test: {
    foo: 1,
  }
  ...
}

Then, in some dispatch, I change the value of test:

nextState.test = { bar: 2 };

With redux-storage set up, this is saved (I guess).

When I now close/reopen or reload the whole app, I have this state:

state = {
  ...
  test: {
    bar: 2,
    foo: 1,
  }
  ...
}

I think, there should be no foo: 1 at this point, should it?

At least it’s bugging me in my app, so what’s the correct way of getting rid of it? Is there a config option for redux-storage that I can set?

(See the whole code here.)

[chandlervdw]

+1, this is very confusing. The previous version this was forked from definitely loaded the stored state upon calling load(store). This seems to fire the REDUX_STORAGE_LOAD action but doesn’t actually update the redux state… is it required to import LOAD from redux-storage in my own reducer?

[anwarhamr]

I was having the same issue, but found it to be a copy/paste mistake. I missed/overlooked/forgot to add the reducer created by storage.reducer(rootReducer) to my call to createStore call. Loading the reducer is the key to all of this happening.

One other issue I’ve found that you want to be careful of, if you persist complex objects for instance Moment, you will need to handle the LOAD event in your reducer and convert it to an object. You can also probably do this using the optional parameters replacer, reviver to createEngine if it supports them; redux-storage-engine-localstorage does.