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

Breaking changes #81

Closed
aksonov opened this issue Jun 8, 2016 · 3 comments
Closed

Breaking changes #81

aksonov opened this issue Jun 8, 2016 · 3 comments

Comments

@aksonov
Copy link

aksonov commented Jun 8, 2016

I'm author of react-native-router-flux and have quite big community here and now we have many problems with breaking changes with almost each new React Native version. We did a lot of efforts to migrate from RN0.22 to RN0.26. And now there is no sense to adopt RNRF to 0.2 because 0.28-rc introduces other breaking changes.

I thought when navigation-rfc became part of RN, its API will be more stable, but i was wrong. Is there any way to clone NavigationExperimental as separate component (navigation-rfc?) until API will be not stable? This way we could stick to specific version of navigation-rfc, and users will not have problems after each RN upgrade.

Is there any roadmap of NavigationExperimenal? When it will be stable?

@jmurzy
Copy link

jmurzy commented Jun 8, 2016

You should watch @ericvicenti's ReactEurope talk. It'll answer most of your questions. In short, there will be no more breaking changes that are as big as what you've experienced in the last few releases. I would say you should still expect some changes here and there until Experimental in the name is dropped.

As for wanting to maintain your own fork of NavigationExperimental, not sure if I'd recommend that but I understand your frustration so here's how you'd do it.

🍺

@ptomasroos
Copy link
Contributor

I agree that the talk give some clear insights on the road ahead

@aksonov
Copy link
Author

aksonov commented Jun 13, 2016

Okey, i've made fork and will use it until API will be stabilized, now RNRF doesn't depend from RN API anymore, so users could upgrade to latest RN without problems.

@aksonov aksonov closed this as completed Jun 13, 2016
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