Using different navigation solution

[heron2014]

@rickardinho

After research we have discovered that there is another navigation plugin (https://github.com/exponentjs/ex-navigation) which is recommended by a member of react-native team (see facebook/react-native#6184 (comment)). The benefits over react-native-router-flux are:

• its structure is closer to the official navigation solution when the native solution is released which makes it more future proof
• it supports lots of extra features like deep linking (see video http://facebook.github.io/react-native/blog/2016/09/08/exponent-talks-unraveling-navigation.html)

We feel it would be best to switch the navigation to ex-navigation. What your thoughts?

[rickardinho]

I'm happy to switch to ExNav if it's not going to eat up too much time. Do we have to do it now or can we wait and get some of the bigger hurdles out of the way first? Or is it better to do it early as it saves time later on?

[heron2014]

Yes, this has to be done early. We are going to do that tomorrow! Shouldn't take too long.

[heron2014]

Additional references about ex-navigation:

• https://gist.github.com/knowbody/ce483742a1761658b767428a0ed35147

[heron2014]

Redirecting and resetting navigation stack

We tried to follow this method for resetting the navigation stack.

We ran into problems - immediatelyResetStack was not a function of our mainNavigator (returned from navigation.getNavigator('main').

Instead, we were able to access immediatelyResetStack as follows, as suggested here:

    navigation.performAction(({ tabs, stacks }) => {
      tabs('main').jumpToTab('feed');
      stacks('confirm').immediatelyResetStack([Router.getRoute('feed')], 0);
    });

.jumpToTab('feed') successfully redirects us to the feed page. We are not sure if the stack is clear or not at this point, nor how to check/inspect it.