Skip to content

fix(core): handle an edge case of changing dependencies without changing atom value #960

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

Merged
merged 7 commits into from
Jan 18, 2022

Conversation

xbaun
Copy link
Contributor

@xbaun xbaun commented Jan 13, 2022

fix #947

(edit by @dai-shi) this is done by a hacky way. wish to have a nicer way.

@vercel
Copy link

vercel bot commented Jan 13, 2022

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/pmndrs/jotai/DRVq3bx1K4pqYauqkpTDx81Ecyeu
✅ Preview: https://jotai-git-fork-xbaun-fix-add-test-case-947-pmndrs.vercel.app

@codesandbox-ci
Copy link

codesandbox-ci bot commented Jan 13, 2022

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 932761f:

Sandbox Source
React Configuration
React Typescript Configuration
React Browserify Configuration
React Snowpack Configuration
Next.js Configuration
Next.js with custom Babel config Configuration
React with custom Babel config Configuration

@dai-shi
Copy link
Member

dai-shi commented Jan 16, 2022

Okay, seems like I was solving a different/general problem. Let's separate that fix in a separate PR and come back to this.

@dai-shi dai-shi changed the title fix: add test case for #947 fix(core): handle an edge case of changing dependencies without changing atom value Jan 16, 2022
@dai-shi dai-shi added this to the v1.5.3 milestone Jan 16, 2022
@dai-shi dai-shi merged commit 3610734 into pmndrs:main Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Regression Bug] Updated atom value not propagated to component
3 participants