-
-
Notifications
You must be signed in to change notification settings - Fork 666
fix(atomWithRefresh): non-writable refreshables throw an error if implicitly passed an argument #2996
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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. |
…tom's setter is called with args
commit: |
|
Playground | Link |
---|---|
React demo | https://livecodes.io?x=id/7V74UHHB8 |
See documentations for usage instructions.
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.
Thanks for your contribution!
…
Related Bug Reports or Discussions
#2995
Fixes #
Summary
Proposed fix for the issue where passing something into the refresh function causes it to do nothing.
Check List
pnpm run fix
for formatting and linting code and docs