-
Notifications
You must be signed in to change notification settings - Fork 2.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
Remove componentWillReceiveProps from Form.jsx #2010
Closed
jimmycallin
wants to merge
11
commits into
rjsf-team:master
from
jimmycallin:no-componentwillreceiveprops
Closed
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
a9d8e05
refactor: form.jsx is no longer using componentwillreceiveprops
2d35019
return null from getDerivedStateFromProps as default
33aee98
change deepEquals to shallow equals in getDerivedStateFromProps
4532e45
checking each key for shallow changes in getDerivedStateFromProps
f26788b
Merge remote-tracking branch 'origin/master' into no-componentwillrec…
28c697c
Merge branch 'master' into no-componentwillreceiveprops
092aab0
Merge branch 'master' into no-componentwillreceiveprops
ed89981
Merge branch 'master' into no-componentwillreceiveprops
jimmycallin 181f0da
Merge remote-tracking branch 'origin/master' into no-componentwillrec…
jimmycallin a40ce16
Revert change for deepEquals function
jimmycallin ed618c9
moved util functions back as static functions to Form
jimmycallin 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
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.
Figure out -- why do we need
lastProps
?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.
On line 62 we need to compare prop changes to determine if the consumer has updated their props.
If the consumer has updated the props, we update the internal state based on the props.
We could previously do this in componentWillReceiveProps since that method supports both viewing previous and new props. But since getDerivedStateFromProps only shows the new prop updates, we need to store the old props in the state.
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.
And the reason why we cannot always derive state from props, is due to us supporting the mixed controlled/uncontrolled behavior we discussed on our last meeting this Friday.