-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Framework: add approach for redux data persistence #3267
Conversation
reducer( browserState, { type: 'DESERIALIZE' } ) | ||
``` | ||
|
||
The key idea is that in the reducer `SERIALIZE` should return a plain JS object. In a subtree that uses Immutable.js |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we explain why it's important to return a JavaScript object?
Because browser storage is only capable of storing simple JavaScript objects, the purpose of the `SERIALIZE` action type reducer handler is to return a plain object representation.
The headings are a bit confusing to the flow of reading:
I might expect it to be structured as:
|
289dd21
to
7057d5a
Compare
0e5671e
to
67dc83a
Compare
I think this looks great... thanks for writing it up! Looks good to 🚢 to me. |
Thanks for the reviews! Going to squash commits. |
67dc83a
to
e22a61b
Compare
Framework: add approach for redux data persistence
Data persistence is still a wip but I think we should update this as we go along.
cc @rralian @mtias @aduth @blowery @dmsnell @ockham