-
Notifications
You must be signed in to change notification settings - Fork 46.9k
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
New commit phase lifecycle: getSnapshotBeforeUpdate #12404
Merged
Merged
Changes from 9 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
f68a77b
Initial pass at getSnapshotBeforeUpdate. More to do.
bvaughn 0f984ac
Moved snapshot value from Fiber to instance (__reactInternalSnapshotB…
bvaughn db84b9a
Use commitAllHostEffects() traversal for getSnapshotBeforeUpdate()
bvaughn 7022568
Added DEV warnings and tests for new lifecycle
bvaughn 47c7afb
Merged master; resolved conflicts
bvaughn 3b1d23c
Merge branch 'master' into getSnapshotBeforeUpdate
bvaughn 55e75da
Don't invoke legacy lifecycles if getSnapshotBeforeUpdate() is define…
bvaughn d4ac106
Fixed a type-check
bvaughn b09b5d2
Merge branch 'master' into getSnapshotBeforeUpdate
bvaughn ca09ef8
Converted did-warn objects to Sets in ReactFiberClassComponent
bvaughn 88d4cac
Replaced redundant new lifecycle checks in a few methods
bvaughn 2428604
Check for polyfill suppress flag on cWU as well before warning
bvaughn ebb6951
Fixed UNSAFE_componentDidUpdate -> componentDidUpdate mistake
bvaughn a13ad52
Added Snapshot bit to HostEffectMask
bvaughn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
Why use
UNSAFE_componentWillReceiveProps
in this test? Just curious—doesn't seem like the test is specifically aboutUNSAFE_componentWillReceiveProps
.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.
I just tried to cover a mix of old and new aliases in the test. There's not really a meaningful pattern to it.
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.
To be clear, these tests are kind of verbose and I was hoping to avoid having to duplicate them for old and new lifecycle aliases, so I just tried to cover a mix of both (so the test could verify that the correct lifecycle name was printed in the warning)