Jump to an existing route?

[jamesfzhang]

Hey @aksonov thanks for creating this router. I've tried Navigator, react-native-router, gb-native-router, and this is definitely the best! Is there a jumpTo functionality like Navigator does? It would transition to an existing scene without unmounting or pushing a new version of the scene onto the route stack. Thanks.

[zebulgar]

Hey @jamesfzhang this is what the type of 'switch' is used for. You can check out in the example how we use it for tabs, however this can be used for any route really. Just define a route as so:

<Route name="foo" type="switch"/>

[zebulgar]

Feel free to reopen if you have further questions

[jamesfzhang]

@MITDelian Thanks, didn't realize that's what "tab" meant!

[zebulgar]

Yes! It's referencing the schema defined up above. If you are having a bunch of routes that have this switching behavior I recommend a schema so you can define other global attributes on said routes if needed

[jamesfzhang]

@MITDelian I tried using type "switch" but I don't want the navbar to appear. I set hideNavBar but it still appears?

<Router hideNavBar={true} style={styles.container}>
  <Schema name='default' sceneConfig={Navigator.SceneConfigs.FloatFromRight}/>
  <Route name='home' component={HomeScreen} initial={true} title='Home' type='replace'/>
  <Route name='tracks' component={TracksScreen} title='Tracks' type='switch'/>
  <Route name='artists' component={ArtistsScreen} title='Artists' type='switch'/>
  <Route name='albums' component={AlbumsScreen} title='Albums' type='switch'/>
</Router>

[aksonov]

Does parent router hide navbar as well?

[jamesfzhang]

@aksonov That is the top level Router.

[jamesfzhang]

@aksonov @MITDelian I added some logging to this library's render method to log the value of hideNavBar in between scene transitions. As you can see the value is true after a push route, which is expected but becomes undefined after a switch route.

[vitalets]

+1 having trouble with unneeded navbar when switch is enabled.