Date being SAVEd is not fully the same data being LOADed. about redux-storage HOT 6 OPEN

Re-opened as @guns2410 want's to work on this project: Give him a warm welcome 👏

from redux-storage.

Sorry for the bad news but this package is no longer maintained. 😞

My focus has left the react / node ecosystem and I don't have to time to keep things up to date. But if you want to step in and become the new maintainer of redux-storage and all of it parts, just ping me! 😃

from redux-storage.

Thanks @michaelcontento

@gijoehosaphat can you confirm what your redux state looks like when you perform these actions. redux-storage saves your exact redux state as is.

from redux-storage.

I can confirm that the when inspecting the data on the action 'REDUX_STORAGE_SAVE' the data looks correct.

When inspecting the data on a subsequent load, the data is incorrect.

In the example above we are adding a new field to the object called status_set, that field seemingly gets dropped, however changes to the already existing fields are retained.

This overall state object structure looks like this:

{
  ...,
  mainKey: {
    ...,
    objectMap: {
      '0': {
        typeKey: [
          { id: 49, status: 'COMPLETE' },
          ...
        ],
        ...
      },
      ...
    },
    ...
  },
  ...
}

from redux-storage.

can you confirm that the reducer to update the state does not remove the key. May be you can post the reducer here and we can have a look.

from redux-storage.

Looks like I'm having the same issue. I believe we could fix this relatively easy by actually doing a SAVE after LOAD on this line. That still heavily depends on the implementation (we have to make sure that we read useful data from localStorage before we rewrite it with the app's initial state). Another solution I'd suggest is just not SAVEing until we LOAD.

from redux-storage.