Skip to content
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

reduxRootKey vs reduxRootSelector #3

Open
sbking opened this issue Feb 22, 2017 · 0 comments
Open

reduxRootKey vs reduxRootSelector #3

sbking opened this issue Feb 22, 2017 · 0 comments

Comments

@sbking
Copy link
Owner

sbking commented Feb 22, 2017

I'm having an issue with the reduxRootKey, which is being deprecated in favor of reduxRootSelector. This opens up the possibility of using arbitrary structures such as Immutable.js to hold your Redux state. Unfortunately, it also means that we have to know how the user is creating the state. Right now, only plain object states are supported. Perhaps in the future, we could add a way for the user to declare how their initial state should be constructed, as well as how it should be serialized and deserialized so the HOC can transfer the state successfully from getInitialProps on the server to the component constructor where it can be rehydrated on the browser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant