Experimental Navigator API

[zebulgar]

@ericvicenti has implemented a new experimental API for Navigation that offers a much more redux-like implementation. I think it's worth looking into building on top of his API, it matches the philosophy of what this library has done in comparison to ExNavigator/Navigator/NavigatorIOS

I'm going to be spending today looking into integrating the two.

facebook/react-native@a308546

https://github.com/ericvicenti/navigation-rfc/blob/master/Docs/Navigation.md

https://github.com/ericvicenti/navigation-rfc/blob/master/Docs/Reducer_Actions.md

[ericvicenti]

Excellent! Let me know how I can help, or if you have any feedback.

Those docs are slightly out of date. I'll update them this afternoon 😄

[zebulgar]

haha no way wasn't expecting an answer so quickly from you. I'm just going through your examples first and making sure I fully understand them.

Was going to email you and ask if you thought this was a good idea but I'll take the comment as implicit approval

[ericvicenti]

I'm happy to see that you're experimenting with it. Bu my hope is that we won't need to rely on many libraries, so people can easily do navigation out of the box with react-native. If you're missing anything important from the built-in Navigation library, please consider sending a PR to react-native so everybody can benefit!

If you want to create custom reducers or navigation views, those would be great to publish independently!

[graywolf336]

@ericvicenti Where can we find the documentation for the Experimental Navigator API? I'm starting to work on a project and am looking into my options for navigation, started to use this repository but then saw this issue and your comments so was just curious. Thanks!

[ericvicenti]

You will probably learn the most by looking through the examples: https://github.com/facebook/react-native/tree/master/Examples/UIExplorer/NavigationExperimental

Right now the docs are quite sparse, but I'm working on them here: https://github.com/ericvicenti/navigation-rfc/tree/master/Docs

If you want to contribute to the docs, that would be very welcome!

[graywolf336]

Okay thanks, I will take a look and try them out.

I won't promise anything, but I will make an effort to if I grasp the understanding of it!

[aksonov]

@ericvicenti Your new experimental API looks very good, but let me explain why i still want to use my component and probably many other people does.

1. I want to have all my routes in one place. Like Storyboard in iOS, but more convenient (because of JSX). I believe navigation logic should be separated from other code.
2. I want to have very simple transitions. Like 'performSegueWithIdentifier' in iOS.

Sorry, maybe it is already done in your API but I've missed it....

[zebulgar]

I have to agree w/ @aksonov.

I've actually been spending some time this last week trying to integrate the best of both APIs. Simple transitions, routes defined in a single place, with a more direct connection to redux similar to react-router-redux.

My goal is to publish it by the end of this weekend and I'd love to get the community's feedback on it. I basically started from @aksonov's library and worked towards an interface similar to the react-router-redux ideology.

[aksonov]

@MITDelian it would be great if you could make it as 'plugin' for this component, like ExRouter.

[zebulgar]

The only real issue with that @aksonov is that I think the stack of the Router class needs to be stored in redux rather than in the state. I'll send you an early version this weekend so you can take a look over it and let me know what you think

[zebulgar]

So there are some slight tweaks I have to make in Actions.js and Router.js in order for it to be more properly "redux" and have all the data stored in the store rather than on a particular component or class state

[aksonov]

We could really make Router (now it is BaseRouter) immutable and its Routes, so it could be stored in state...

[danielweinmann]

+1!

[zebulgar]

Yes! That is what I'm working on @aksonov

[zebulgar]

I have all of the adjustments made to the rest of the codebase as if BaseRouter was immutable, and now I need to actually move the stack to the store and make it so the logic for pop, jump etc are in the reducers rather than in the class