-
-
Notifications
You must be signed in to change notification settings - Fork 622
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
feat(devtools): read-only atom support in useAtomDevtools #817
feat(devtools): read-only atom support in useAtomDevtools #817
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/pmndrs/jotai/DWZndSUYFFTznovf7kwXoR5ZADNv |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 21cf8af:
|
@dai-shi I think it's ready for review now! https://codesandbox.io/s/react-typescript-forked-q3fwd?file=/src/App.tsx |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall looks good. just minor suggestions.
Co-authored-by: Daishi Kato <dai-shi@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few questions before finishing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me. Will merge it when we release it.
Thanks! |
Previously,
useAtomDevtools
only accepts primitive atoms (more preciselyWritableAtom<Value, Value>
type). Now, with this PR, it supports read-only atoms (Atom<Value>
type).close #808