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
The docs specify The callback is not called due to changes from this effect's own setSelf()
The callback is not called due to changes from this effect's own setSelf()
However, this does not apply when setSelf is called with a promise. I've made a CodeSandbox to demonstrate: https://codesandbox.io/s/atom-effects-triggers-own-onset-gy1ty
The text was updated successfully, but these errors were encountered:
may be fixed with #979
Sorry, something went wrong.
@ShravanSunder - looks like a slightly different cause. But, I have a fix with #986
Avoid calling onSet() when setSelf() initializes with a Promise
9bb25b5
Summary: Fixes facebookexperimental#953 Avoid calling onSet() when setSelf() initializes with a Promise. Differential Revision: D27975202 fbshipit-source-id: 2110733710d084b0b0a9f89334e6688467069993
Avoid calling onSet() when setSelf() initializes with a Promise (face…
cbec7a9
…bookexperimental#986) Summary: Pull Request resolved: facebookexperimental#986 Fixes facebookexperimental#953 Avoid calling onSet() when setSelf() initializes with a Promise. Differential Revision: D27975202 fbshipit-source-id: 4560fb92fe549c31340092b351a85dc6ae400b52
e63e8ac
drarmstr
Successfully merging a pull request may close this issue.
The docs specify
The callback is not called due to changes from this effect's own setSelf()
However, this does not apply when setSelf is called with a promise. I've made a CodeSandbox to demonstrate:
https://codesandbox.io/s/atom-effects-triggers-own-onset-gy1ty
The text was updated successfully, but these errors were encountered: