search

ericvicenti / navigation-rfc

Better Navigation in React Native
441 stars 44 forks source link

Breaking changes #81

Closed aksonov closed 8 years ago

aksonov commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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

aksonov commented 8 years ago

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.