-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Snapshot.getDeps_UNSTABLE has been removed in recoil 0.2.0 #136
Comments
Any workarounds for this issue ? :) |
Same problem, any help please? 👍 |
@TheMadKow while waiting for the update, you can modify the index.js file by replacing : nodes.forEach(node => { Thanks, @kevintap-idemia for the help ;) |
@Sammyham Thanks for the solution! |
Done #140 |
It would be great to get this PR merged - we're having to manually update the index.js everytime we add recoilize, and it's getting a bit tiresome. The work is already done, just needs merging. |
I suspect that this is not being merged due to backwards compat concerns. The PR would allow compatibility with recoil 0.2.0+, but would then break compatibility with older recoil releases (0.1.3), which is the current stated compatible/tested recoil release in the docs for the recoilize 2.0.1 release. Perhaps @Sammyham if you re-work your PR to allow backwards compat, this might be simpler to merge? |
Thank you for the workaround! |
follwing open-source-labs#136
Is this issue fixed? because I also tried to add this change in the index.js file and the chrome extension just crashed! |
I believe the PR which fixed this issue was merged (#140), and it would be included inside the release of v3.0.0 if it comes in the near future as planned. |
I'm getting another error after I updated the getDeps function:
with the function:
Is this because I'm using React 18? |
This is still an issue |
Recoilize/package/index.js
Line 59 in 96db24b
Snapshot.getDeps_UNSTABLE has been removed in recoil 0.2.0. This API changed to Snapshot.getInfo_UNSTABLE().deps. Recoilize needs to be updated here to be compatible with the latest recoil 0.2.0 release.
The text was updated successfully, but these errors were encountered: