We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As a part of looking into improvements for useAtomCallback, I've stumbled upon a issue, see the CodeSandbox reproduction.
useAtomCallback
It looks like there's a freeze, when I click one of those listitems, and Jotai starts to update a bunch of async read atoms.
I've added some tests on a branch, where the tests passes, but you get warnings about [Bug] deleting atomState with read promise.
[Bug] deleting atomState with read promise
I'm looking into this help with the help of @dai-shi, so I created this issue for tracking/transparency.
The text was updated successfully, but these errors were encountered:
dai-shi
Thisen
Successfully merging a pull request may close this issue.
As a part of looking into improvements for
useAtomCallback
, I've stumbled upon a issue, see the CodeSandbox reproduction.It looks like there's a freeze, when I click one of those listitems, and Jotai starts to update a bunch of async read atoms.
I've added some tests on a branch, where the tests passes, but you get warnings about
[Bug] deleting atomState with read promise
.I'm looking into this help with the help of @dai-shi, so I created this issue for tracking/transparency.
The text was updated successfully, but these errors were encountered: