-
Notifications
You must be signed in to change notification settings - Fork 10
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
Immutable root state #37
Comments
Sounds interesting! I skimmed through the other PR and through redux-offline-immutable-config. The only thing I'm not thrilled about, is that even if one's not dealing with an immutable store, there's a slight overhead introduced to the core because of the lenses. |
On another note, the redux-offline org seems like a good place where your config package could live in. |
It looks good. About as compact a change as I think possible. Injecting As for the lens, you are either going to need such an abstraction or to build two versions of the project. I prefer adding an abstraction. |
That said I don't understand the benefit of making the root object immutable. |
Thanks for all comments.
When using immutable setting the entire redux state as immutable is a best practice:
I will go through the rebase and see if there are any incompatibilities |
Hi @sorodrigo,
thanks a lot for opening and maintaining this repository.
A couple of months ago I opened this PR: redux-offline#99
to allow the use of
immutable root state
withredux-offline
.Since then we have been successfully using the fork with our immutable root state.
I wanted to check with you whether the same PR could be merged in this fork if I create it and rebase it in top of the current improvements.
Thanks
The text was updated successfully, but these errors were encountered: