You can make your own router by building an object with the following functions:
Defines the navigation state in response to a given action. This function will be run when an action gets passed into
props.navigation.dispatch(, or when any of the helper functions are called, like
Typically this should return a navigation state, with the following form:
If the router has handled the action externally, or wants to swallow it without changing the navigation state, this function will return
Returns the child component or navigator for the given route name.
Say a router
getStateForAction outputs a state like this:
Based on the routeNames in the state, the router is responsible for returning valid components when calling
Returns the active component for a deep navigation state.
Returns an optional navigation action that should be used when the user navigates to this path and provides optional query parameters.
Returns the path and params that can be put into the URL to link the user back to the same spot in the app.
The path/params that are output from this should form an action when passed back into the router's
getActionForPathAndParams. That action should take you to a similar state once passed through
Used to retrieve the navigation options for a screen. Must provide the screen's current navigation prop and optionally, other props that your navigation options may need to consume.
navigation- This is the navigation prop that the screen will use, where the state refers to the screen's route/state. Dispatch will trigger actions in the context of that screen.
screenProps- Other props that your navigation options may need to consume
navigationOptions- The previous set of options that are default or provided by the previous configurer
Inside an example view, perhaps you need to fetch the configured title: