You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we're starting to implement redux-persist. We just released this library Normalizr-immutable that basically converts a javascript object to a normalized structure using Records, Lists and Maps and converts it back to the original in-going Js object (in that sense it is different from Normalizr).
So, we are wondering if we should try to implement redux-persist-transform-immutable or just take the persisted js object and run it through normalizr-immutable and then populate the reducer.
Do you see any advantages in one over the other method?
The text was updated successfully, but these errors were encountered:
Hi, we're starting to implement redux-persist. We just released this library Normalizr-immutable that basically converts a javascript object to a normalized structure using Records, Lists and Maps and converts it back to the original in-going Js object (in that sense it is different from Normalizr).
So, we are wondering if we should try to implement redux-persist-transform-immutable or just take the persisted js object and run it through normalizr-immutable and then populate the reducer.
Do you see any advantages in one over the other method?
The text was updated successfully, but these errors were encountered: