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

Confusion to new comer: what version shall I use? #2041

Closed
oeddyo opened this issue Jul 16, 2017 · 4 comments
Closed

Confusion to new comer: what version shall I use? #2041

oeddyo opened this issue Jul 16, 2017 · 4 comments

Comments

@oeddyo
Copy link

oeddyo commented Jul 16, 2017

Thanks for the great work of putting up this amazing tool together.

As a new comer to this tool, I'm overwhelmed by the version changes and on going doc improvements. My question is, since V4 is in beta, and a lot of APIs are changing (correct me if I'm wrong), what version shall we use in production?

Thanks!

@oeddyo
Copy link
Author

oeddyo commented Jul 16, 2017

To be more specific, in V3's doc page, the API page is giving 404. And in V4's doc page, seems the author is still working on it :|

@diegocouto
Copy link
Contributor

Hi, @oeddyo I think that it depends on what you're building. If it's an iOS only app, I'd definitely go with v4 (React Navigation transitions are a delight). On the other hand, if you need Android compatibility, v4 can't be used without workarounds.

@oeddyo
Copy link
Author

oeddyo commented Jul 16, 2017

Thanks a lot @diegocouto for commenting!

We are actually building for both android & ios. Thus I guess the option for us is to go with v3 then...

Thank you!

@aksonov
Copy link
Owner

aksonov commented Jul 16, 2017

@oeddyo I see your confusion - v4-beta or unsupported-v3. This problem is going from quite strange React Native team behaviour - stop to support existing navigation and ask community for migration to beta ReactNavigation package. So I v4-beta is the same quality as beta React Navigation. If it works differently for Android comparing to React Navigation then it is VERY strange because RNRF is just wrapper - you may check source codes - it just creates needed component tree and configuration for ReactNavigation. Probably the problem that Android doesn't support passing functions/images as parameters to actions (because images are passing now via props)? It is necessary just to debug it to find the reason...

@aksonov aksonov closed this as completed Jul 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants