-
Notifications
You must be signed in to change notification settings - Fork 48.2k
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
[fail] Only warn on unacted effects for strict / non sync modes #16041
Merged
threepointone
merged 2 commits into
facebook:master
from
threepointone:unacted-effects-warning-strict-mode-only
Jul 3, 2019
Merged
[fail] Only warn on unacted effects for strict / non sync modes #16041
threepointone
merged 2 commits into
facebook:master
from
threepointone:unacted-effects-warning-strict-mode-only
Jul 3, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(basically, when `fiber.mode !== 0b0000`) Warnings on unacted effects may be too noisy, especially for legacy apps. This PR fires the warning only when in a non sync mode (concurrent/batched), or when in strict mode. This should make updating easier. I also added batched mode tests to the act() suite.
No significant bundle size changes to report. Generated by 🚫 dangerJS |
acdlite
reviewed
Jul 2, 2019
acdlite
approved these changes
Jul 2, 2019
threepointone
commented
Jul 3, 2019
threepointone
force-pushed
the
unacted-effects-warning-strict-mode-only
branch
from
July 3, 2019 00:19
5d2fb1e
to
394ce77
Compare
trueadm
pushed a commit
to trueadm/react
that referenced
this pull request
Jul 3, 2019
…book#16041) * only warn on unacted effects for strict / non sync modes (basically, when `fiber.mode !== 0b0000`) Warnings on unacted effects may be too noisy, especially for legacy apps. This PR fires the warning only when in a non sync mode (concurrent/batched), or when in strict mode. This should make updating easier. I also added batched mode tests to the act() suite. * explicitly check for modes before warning, explicit tests for all modes
Merged
This was referenced Aug 17, 2019
This was referenced Mar 10, 2020
This was referenced Mar 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(basically, when
fiber.mode !== 0b0000
)Warnings on unacted effects may be too noisy, especially for legacy apps. This PR fires the warning only when in a non sync mode (concurrent/batched), or when in strict mode. This should make gradually updating codebases easier too.
I also added batched mode tests to the act() suite.