Remove usage of UNSAFE React method #177
Merged
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
Methuselah96
changed the title
Methuselah96
changed the title
|
Thanks @Methuselah96 |
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.
This could be considered a breaking change since the peer dependencies on React were updated, however the breaking change was actually in #167 since it uses
UNSAFE_componentWillReceivePropswhich was introduced in[email protected].getDerivedStateFromPropswas also introduced in[email protected]which is what this PR uses.I also went ahead and added
[email protected]to the peer dependency range since I was already updating the value.Peer dependency on React:
react@^0.14.9 || ^15.3.0 || ^16.0.0-rc || ^16.0=>react@^16.3.0 || ^17.0.0.Resolves #163.