[Feature Request] Trace source of atom updates #135
Closed
kevinschaich
started this conversation in
Ideas
Replies: 3 comments
-
Thanks for reaching out! This feature has been on my mind for a while now. Perhaps something I can look into after adding support for Jotai store v2. Open to PRs if you have ideas as well 🙌 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hey @arjunvegda wanted to check in. Do you have any ideas on how we'd implement this? Happy to do what I can to contribute |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When your state becomes large enough, effects tend to overlap – especially in applications with a lot of visual/input interactions (mouse movement, tracking positions of elements on the screen, dragging and dropping, etc). This can lead to render loops that can be hard to track down. If you have 10 buttons/sliders/keyboard shortcuts that all perform the same state update, it's really time consuming to figure out which one of them is causing issues.
Redux devtools has a nice feature that lets you "trace" the source of updates:
I think this would be a nice addition to the devtools, perhaps in the Time Travel tab behind a (default off) feature flag or setting.
Beta Was this translation helpful? Give feedback.
All reactions