-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set up help #15
Comments
It looks like this line |
@rt2zz thanks man, ah didnt realise that was in the pipeline. Will keep an eye out! |
@rt2zz just wondering if theres any timeline on the immutable support you mentioned? |
Not sure, potentially this weekend! |
@rt2zz : not sure what you have planned, but it would be great if the coming changes were seamless-immutable compatible. The API is almost the same. |
Ok tentative immutable support for redux-persist now available at https://github.com/rt2zz/redux-persist-immutable. note I have not actually run this in an app, but the tests pass ;) |
@braco if you can weigh in on what changes are needed for seamless-immutable support, I believe it should be easy to add in. Right now we reply on Map.get() in particular |
Paging @rtfeldman |
@rt2zz: where's the code currently residing so I can take a look? |
@braco code in question is here: https://github.com/rt2zz/redux-persist-immutable |
My components use plain javascript objects as their props am I right in thinking that I only need to use
redux-persist-transform-immutable
and notredux-persist-immutable-state
?When trying to implement
redux-persist-transform-immutable
im getting an error, when the persistStore function gets run its turning the state from an Immutable.Map into a JS object version of the Immutable.Map, which is causing thesyncHistoryWithStore
to give the error in the console.Any help would be great!
Thanks
Persister HOC (
persistStore
gets run on componentWillMount)Instructions from
redux-immutable
:Store configuration:
The text was updated successfully, but these errors were encountered: