-
Notifications
You must be signed in to change notification settings - Fork 23
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
Last Redux State is not written to disk #35
Comments
So the default debounce is 1000ms, do you wait that long at least? |
This was referenced May 19, 2017
Yes, i did |
If i change all the _.clone to _.cloneDeep as discussed in #36 , the problem is solved, but this would be too expensive. |
Same issue |
Still an issue on the latest version? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @JulianKingman , this is the last action that modifies the redux state and after that, we have 9 resources stored in state.
But when we shut down the server and then refresh the app,
![screen shot 2017-05-18 at 3 17 47 pm](https://cloud.githubusercontent.com/assets/26317142/26187566/5c9bd26a-3bdd-11e7-8d62-e63c35f31e11.png)
persist/REHYDRATE
only carries 6 of them, as shown below,Wondering the last redux state should be written to disk in the debounce time?
Or this is caused by redux-persist? Please see:
rt2zz/redux-persist#350
rt2zz/redux-persist#355
The text was updated successfully, but these errors were encountered: