Skip to content
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

v2 Roadmap #1263

Closed
grabbou opened this issue Apr 26, 2017 · 12 comments

Comments

@grabbou
Copy link
Collaborator

@grabbou grabbou commented Apr 26, 2017

Note: We are currently working on v1 - you can track progress in #723. Once completed, we will start implementing issues below.

For the second release, lets focus on new ways of customising transitions, and overriding navigation components.

  • Support custom transitions per screen #175

We look forward to your feedback. Feel free to suggest important features you'd like to see in next release.

@grabbou grabbou referenced this issue Apr 26, 2017
3 of 9 tasks complete
@wilomgfx

This comment has been minimized.

Copy link

@wilomgfx wilomgfx commented Apr 26, 2017

I think releases and goals like this should be inside a project. It would make it easier to follow and find.

@ericvicenti ericvicenti changed the title Road to v2 stable v2 Roadmap Apr 26, 2017
@necolas

This comment has been minimized.

Copy link

@necolas necolas commented Apr 26, 2017

I'd like to make a suggestion: to get react-navigation working with react-native-web. RNW implements much of the RN API and we should be able to support the full feature set of react-navigation on web for people using RNW.

@nico1510

This comment has been minimized.

Copy link
Contributor

@nico1510 nico1510 commented Apr 27, 2017

Not really a feature but the issue with the StackNavigator rendering too many screens is a blocking issue for anyone who wants to bring an android app into production.

@vomchik

This comment has been minimized.

Copy link

@vomchik vomchik commented Apr 27, 2017

@nico1510 it's really blocker for more developers(

@matthamil

This comment has been minimized.

Copy link
Member

@matthamil matthamil commented Apr 27, 2017

@wilomgfx see #561. For the remainder of v1, it looks like they are going to rely on issues. See #723 for the v1 roadmap.

@rafayepes

This comment has been minimized.

Copy link

@rafayepes rafayepes commented Apr 27, 2017

I'd like to define StackNavigator mode at route, instead of Navigator level. Somehow, related to #175

@MovingGifts

This comment has been minimized.

Copy link

@MovingGifts MovingGifts commented Apr 28, 2017

  1. Use replace functionality when navigating to replace the current scene.
  2. Prevent push more than once when tapping navigation button too fast.
@MovingGifts

This comment has been minimized.

Copy link

@MovingGifts MovingGifts commented Apr 30, 2017

  1. Add default undefined params key to navigation state (whether params exist or not).
  2. Animate showing/hiding of tabbar when using this.props.navigation.setParams({ tabBarVisible: true/false });
@annelorraineuy

This comment has been minimized.

Copy link

@annelorraineuy annelorraineuy commented May 5, 2017

When the app is RTL (Farsi/Hebrew, etc), the issue where the drawer nav is open and on screen on hide is important to address as well. This limits apps using drawers from being fully localization-ready for production. #270

@shirbr510

This comment has been minimized.

Copy link

@shirbr510 shirbr510 commented Jun 14, 2017

any news about #706 ?
might count as stable if it will be pushed to V1

@efkan

This comment has been minimized.

Copy link

@efkan efkan commented Jun 20, 2017

Caching screens according to their NavigationOptions would be great.
Especially when working with DrawerNavigator on screens -that have a lot of control or have a map component.
Currently the components re-render when the stack is changed. This causes to lost the entered values or position of the map.

For instance, when getting back to a screen by using headerLeft back button which performs a this.props.navigation.goBack(null) method everything is OK. The all components same with how they were before leaving.

@matthamil

This comment has been minimized.

Copy link
Member

@matthamil matthamil commented Sep 15, 2017

Closing in favor of #2585

@matthamil matthamil closed this Sep 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.