Renewed Path to React Navigation V1.0

[matthamil]

A (Renewed) Path to React Navigation V1

Blog post about the new roadmap. The blog post introduces the many awesome community members who have stepped up to revitalize this project.

Below lists the updated roadmap to 1.0 for react-navigation. The roadmap has been updated to include issues that received positive feedback from the community. For reference, the old roadmap can be found here.

---

Renewed Roadmap to 1.0

• Updated and improved documentation website
• Add ex-navigation style StackNavigator actions New StackRouter Push Action #3401 StackRouter PopToTop Action #3403 StackRouter PopN Action #3404
• Improve Reset NavigationAction proposal/fix: StackNavigator RESET action replaces with no animation unless action.direction = 'back' | 'forward' is supplied #1663
• Navigate key for idempotent pushes Add optional key to navigate action, allowing idempotent pushes #135
  • Proposals Make sure dispatch can be called multiple times per-tick #1313, queued transitions #2400, Fix idempotent pushes during transition. #2578
• Resolve go back issues: goBack issues #2454
• Screen lifecycle hooks screenIsActive prop / componentDidFocus event for TabNavigator items #51
• Fix issues with drawer navigator - Drawer causes header title to disappear, possibly has wrong font #374
• Allow multiple Drawers creating two sidemenu or drawers navigator #780

Resolved issues from original roadmap:

• Header bar overriding Make header configurable #1220
• Resetting non-deepest navigator Specify reset key to define what state should be reset #691
• Simplified Nav Options RFC: Simplified Navigation Options #722

Look at this later

• Fix inter-navigator issues Integration between different navigators #88
• Add customizable per-screen transitions Support customizable, complex transitions that animate individual views on a screen #175, StackNavigator: Allow configurable, different transition animations between screens #124, Modal StackView nested inside other StackNavigator is not presented modally #690, mode prop for Screen #232, Choose transition mode for each screen in StackNavigator #707, make a specific screen a modal? #770

---

How can you help?

We need your help to reach 1.0. For the time being, we will be prioritizing PRs that help the community reach 1.0.

There are many ways to contribute without writing a PR:

1. When opening a new Issue, fill out the Issue Template. This helps maintainers and the community at large to resolve your issue quickly.
2. Close issues that are now resolved.
3. Answer questions in the Issues.
4. Ask questions on StackOverflow and in the Reactiflux community Discord (and answer questions there too :)).
5. Review PRs by asking questions about changes made to stimulate conversation.

Ultimately, the path to 1.0 will take time. We hope to quickly bring the library up to speed again.

[plasticine]

@matthamil fantastic — thanks for the update, and looking forward to the post.

Feel free to take this as a comment, but I’d really like to see (and would be interested in contributing) a more robust, integration level set of tests to this library. Examples are good, but are not the right tool to prove functionality and prevent regressions—especially as the collaborators attempt to tackle the above roadmap...

I would strongly urge you to tackle this as a matter of priority as it will make the project as a whole more accessible and reliable.

❤️

[allmaxgit]

Tabs connected to Redux on android very slow. Please add it fix in Roadmap.

[matthamil]

Do you have an open issue for this problem @allmaxgit?

[allmaxgit]

@matthamil #739

[younanjo]

@matthamil any chance this guy can be looked into as part of the roadmap? #1493

[matthamil]

Although not a roadmap issue, this is something I'd like to see addressed as well @younanjo. There's an open PR for it that needs review #2520. Always open to other solutions that the community comes up with.

[koenpunt]

Dynamic routes and/or options for TabNavigator (and other navigators) would be nice; currently I have to jump through all kinds of hoops to get this working.

Because for example, there are ways to show less tabs than there are screens, by using a custom tabBarComponent. But then the screen still exists, which means you can still swipe to the "invisible" tab. I worked around that by actually reimplementing the TabNavigator (copy/paste), and overriding swipeEnabled with true when not all tabs should be accessible, but this obviously is not desirable.

[ferrannp]

What do you think about improving Android transitions? They are totally off right now comparing to native. See #726.

[Ashoat]

I would love if we could actually fix Flow types for react-navigation. I will do this if somebody promises to actually review my PR.

The issue is that a stock React Native app with Flow enabled will have dozens of Flow errors once you install and require react-navigation. More details here, but this has been the case for months. I have tried addressing it before, but nobody has actually reviewed my PRs.

I really think 1.0 should be able to install on a stock React Native app without any Flow errors.

[sospedra]

From reviewing our code looking for our hacky solutions. I make this list with the workarounds we believe shall be covered by the lib:

• Are we taking reset as part of the goBack issue? If not, I think it's very important and requested Flicker during navigation reset #639 Reset stack from other stack inside tab #2291
• Prevent navigating twice to the same rotue + params Add optional key to navigate action, allowing idempotent pushes #135 Don't render twice when goBack and re navigate on same screen #2331 Screen mount twice when go back and quickly re navigate to same screen  #2396
• Connect component's props with navigationOptions (avoid hacky and unresponsive setParams on any React lifecycle hook)
• Navigate to any nested navigator shouldn't be a problem (Not finding the routeName)
• Instead of break the app when a route isn't found allow a 404/Miss
• Android performance StackNavigator has performance issues and renders too many screens #706 Stacknavigator transition extremely slow #608 Android native transition between screens #726
• Reset parent navigationOptions when goBack There is no way to reset a parent's navigationOptions when navigating back in the StackNavigator #2309

And my personal advice:

• Heavily improve test suite and CI

About the roadmap to v1. IMHO, I feel like it's too ambitious. The current state of the issue's list is very prone to fail cause overwhelm. Can we think about break it into smaller milestones?