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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: