Skip to content

fix: use react-native convention for version overrides, allows AndroidX to work - #201

Merged
sumedht merged 1 commit into
razorpay:masterfrom
mikehardy:allow-version-overrides
Jun 19, 2019
Merged

sumedht merged 1 commit into
razorpay:masterfrom
mikehardy:allow-version-overrides

Conversation

@mikehardy

Copy link
Copy Markdown
Contributor

This implements the standard way that react-native modules allow for overrides, and moves the default to 28 so AndroidX will work, otherwise users can't jetify your library and use AndroidX dependencies.

Mentioned here: react-native-netinfo/react-native-netinfo#107 (comment)

@mikehardy

Copy link
Copy Markdown
Contributor Author

@pronav if you can look at this and merge it, it'll help users - there are compile fails happening now related to it unfortunately

@rocknegi

Copy link
Copy Markdown

@mikehardy working fine now

@sumedht
sumedht merged commit ba399b1 into razorpay:master Jun 19, 2019
@pronav

pronav commented Jun 19, 2019

Copy link
Copy Markdown
Contributor

Thanks @mikehardy for the neat fix!

@mikehardy

Copy link
Copy Markdown
Contributor Author

Happy to help - this actually helped me strengthen my tests for jetifier, and now that it's resolved everyone benefits on both sides. Cheers

@mikehardy
mikehardy deleted the allow-version-overrides branch June 21, 2019 17:17
@mikehardy

Copy link
Copy Markdown
Contributor Author

@pronav @sumedht React-Native 0.60 is in RC3 now, and will be released in the next couple days, if you don’t release this change, use of your library will result in broken builds for those using jetifier, the recommended way for developers to migrate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants