Support for assigning to this.state inside componentWillReceiveProps#9040
Merged
acdlite merged 5 commits intofacebook:masterfrom Feb 22, 2017
Merged
Support for assigning to this.state inside componentWillReceiveProps#9040acdlite merged 5 commits intofacebook:masterfrom
acdlite merged 5 commits intofacebook:masterfrom
Conversation
We don't explicitly support this but it happens to work in Stack. We'll give it the same semantics as replaceState.
...without dropping the update. This won't work the other way around, if you assign to this.state before calling setState. we'll add a deprecation warning so people stop relying on this pattern.
We'll remove support for this in a future release, though we'll likely still warn.
Tightens up the test a bit to prevent regressions.
sebmarkbage
approved these changes
Feb 22, 2017
This file contains hidden or 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
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.
We don't explicitly support this pattern, but it happens to work (kinda) in Stack. We'll give it
replaceStatesemantics and print a warning so that people stop relying on this pattern. In the future we'll remove thereplaceStatebehavior but keep the warning.