Closed rubikzube closed 7 years ago
Yes, this is intentional (sorta). As stated in the README, we only maintain support for the most recent versions of react-native, if youre using an older version, you will need to use an older version of react-native. There isnt a definitive guide as to what versions work with what, but if you look at the Releases, it should be simple enough to figure out. I will work on some kind of table at some point.
I get where you're coming from, but if the intent is to deprecate support for consumers using older version of react, would this set of changes count as a breaking change and therefore a major version bump instead of a patch bump?
Technically yes, if we followed semver, but as react has introduced hundreds of breaking changes as version releases, i'm not fussed. Either way that's what we support, it'd be almost impossible to support all versions of react-native at the same time on a library like this
Error found in 0.2.9 but not in 0.2.8
Currently using: