-
-
Notifications
You must be signed in to change notification settings - Fork 651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade react-navigation to v3 #3649
Comments
Release notes, since we don't already have them linked here: Note that installation has gotten a bit more complicated: |
@gnprice I would like to do this. Can I? |
@awasthishubh I've just assigned you #3700, which you claimed there; let's start with that. 🙂 |
|
It appears that FlowTyped does have a libdef for this version! So we very likely won't have to use Flowgen for this upgrade. |
(Moved a large comment to my PR: #4249 (comment)) |
In this commit: - Update react-navigation and its libdef, handle breaking changes in code - Update react-navigation-redux-helpers to keep compatibility; handle breaking changes and let it wrap AppNavigator in its preferred way - Add react-navigation-stack and react-navigation-drawer to prepare for the requirement in v4 that we depend on these directly. Match the versions of these (and that of react-navigation-tabs, which we're already depending on) to the versions react-navigation v3 has for these in its `dependencies` in its `package.json`. Grab a compatible libdef for react-navigation-stack. - Add @react-navigation/core, @react-navigation/native, and react-native-gesture-handler to satisfy peer dependencies. Follow instructions for some additional setup for react-native-gesture-handler in Jest config and `MainActivity.kt`. - Add a note about a console error that we're getting, which will go away in react-navigation v4. It doesn't seem to break any functionality. See more detail on GitHub [TODO: add link here]. Fixes: zulip#3649
In this commit: - Update react-navigation and its libdef, handle breaking changes in code - Update react-navigation-redux-helpers to keep compatibility; handle breaking changes and let it wrap AppNavigator in its preferred way - Add react-navigation-stack and react-navigation-drawer to prepare for the requirement in v4 that we depend on these directly. Match the versions of these (and that of react-navigation-tabs, which we're already depending on) to the versions react-navigation v3 has for these in its `dependencies` in its `package.json`. Grab a compatible libdef for react-navigation-stack. - Add @react-navigation/core, @react-navigation/native, and react-native-gesture-handler to satisfy peer dependencies. Follow instructions for some additional setup for react-native-gesture-handler in Jest config and `MainActivity.kt`. - Add a note about a console error that we're getting, which will go away in react-navigation v4. It doesn't seem to break any functionality. See more detail on GitHub at zulip#4249 (comment). Fixes: zulip#3649
In this commit: - Update react-navigation and its libdef, handle breaking changes in code - Update react-navigation-redux-helpers to keep compatibility; handle breaking changes and let it wrap AppNavigator in its preferred way - Add react-navigation-stack and react-navigation-drawer to prepare for the requirement in v4 that we depend on these directly. Match the versions of these (and that of react-navigation-tabs, which we're already depending on) to the versions react-navigation v3 has for these in its `dependencies` in its `package.json`. Grab a compatible libdef for react-navigation-stack. - Add @react-navigation/core, @react-navigation/native, and react-native-gesture-handler to satisfy peer dependencies. Follow instructions for some additional setup for react-native-gesture-handler in Jest config and `MainActivity.kt`. - Add a note about a console error that we're getting, which will go away in react-navigation v4. It doesn't seem to break any functionality. Also, run `yarn yarn-deduplicate && yarn` as prompted by `tools/test deps`. See more detail on GitHub at zulip#4249 (comment). Fixes: zulip#3649
Forking this out from #3573. Probably I should have made separate issues in the first place.
We use
react-navigation
for navigation in the app. We're on version 2.18.3. There's a new major version out, v3. (We were on v1 until not long ago; getting to v2 was #3573.)The v3 releases contain various bugfixes, as well as compatibility with newer other software. Issues blocked on this upgrade include #3569, and possibly #2716 and #3566.
There's partial work toward this issue in #3502.
The text was updated successfully, but these errors were encountered: