-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Review another state management #68
Comments
came upon this repo: https://github.com/dai-shi/will-this-react-global-state-work-in-concurrent-mode @JeremyRH looks like zustand's event emitter implementations will cause problems in concurrent mode? also, curious, is there a reason you guys decided against using context API with proxies? |
shallow copies have subtle but interesting properties, for instance knowing from the root up which nodes have changed till the very last atomic. i always felt like it's a very simple but powerful concept that transcends languages - and if someone wants proxies: immer. as for tearing, i've read up on it and bumped into the following written by @markerikson
i like the levelheaded approach. it's fine to go and look what the problem could be, but i think it's too early to panic. |
@alidcastano Creating a deep copy of the state, storing it in a ref, and updating it in |
Closing this as it's stale. Please file a new issue for further discussion. |
Please, review https://github.com/zerobias/effector and https://github.com/artalar/reatom
The text was updated successfully, but these errors were encountered: