You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent React Navigation v5 has similar syntax to RNRF but it still requires definition of separate variables for every nested stack/tab, it is not convenient.
I've started RNRF v5 development (full rewriting to use React Navigation v5), but really need help to complete this huge task.
Benefits comparing to RN v5:
The same RNRF API as for previous versions, you don't need to rewrite your app!
Latest features from RN v5
Define all scenes in one place. No need to define separate variable as RN v5 does
Define onEnter/onExit actions in one place (like in v4 ). For v5 I'm planning to integrate state machine - https://xstate.js.org, so you may define authentication and other workflows together with your screens
Hello folks!
Recent React Navigation v5 has similar syntax to RNRF but it still requires definition of separate variables for every nested stack/tab, it is not convenient.
I've started RNRF v5 development (full rewriting to use React Navigation v5), but really need help to complete this huge task.
Benefits comparing to RN v5:
You may check https://github.com/aksonov/react-native-router-flux/tree/v5 as prototype, it supports now pretty limited actions and props, but already works and I'm using it in one my new project
The text was updated successfully, but these errors were encountered: