Open macrozone opened 6 years ago
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
^
^1.0.0
2.0.0
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.
^0.21.0
0.21.x
0.22.0
changing the version of recompose dependency
to avoid duplicate in client code
same as before
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