Silent initial field registration to avoid React warning#766
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #766 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 17 17
Lines 251 251
Branches 58 58
=========================================
Hits 251 251
Continue to review full report at Codecov.
|
Member
Author
|
Published in |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
As of React
v16.13.0, there has been a warning. Inv16.13.1, they pointed it directly to https://fb.me/setstate-in-render (react/react#18178 (comment)).This PR fixes the problem by using a new feature in
[email protected]that allows "silent" field registration that does not notify everyone else. Interestingly, this should also be a performance improvement for adding new fields.Fixes #751.