relax recompose dependency #823
Open
Conversation
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
to avoid ending up with duplicated versions of recompose. the carret `^` usually only cares about the first version number, so `^1.0.0` won't match `2.0.0` but any of `1.x.x` BUT: this is not true, if it starts with 0. Then, `^0.21.0` will match any `0.21.x` but not `0.22.0` or higher.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
to avoid ending up with duplicated versions of recompose.
the carret
^usually only cares about the first version number, so^1.0.0won't match2.0.0but any of1.x.xBUT: this is not true, if it starts with 0. Then,
^0.21.0will match any0.21.xbut not0.22.0or higher.Griddle major version
Changes proposed in this pull request
changing the version of recompose dependency
Why these changes are made
to avoid duplicate in client code
Are there tests?
same as before