Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/custom-navigators.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ The navigation prop passed down to a navigator only includes `state` and `dispat

All navigators are controlled components: they always display what is coming in through `props.navigation.state`, and their only way to change the state is to send actions into `props.navigation.dispatch`.

Navigators can specify custom behavior to parent navigators by [customizing their router](/docs/custom-routers/). For example, a navigator is able to specify when actions should be blocked by returning null from `router.getStateForAction`. Or a navigator can specify custom URI handling by overriding `router.getActionForPathAndParams` to output a relevant navigation action, and handling that action in `router.getStateForAction`.
Navigators can specify custom behavior to parent navigators by [customizing their router](/docs/custom-routers). For example, a navigator is able to specify when actions should be blocked by returning null from `router.getStateForAction`. Or a navigator can specify custom URI handling by overriding `router.getActionForPathAndParams` to output a relevant navigation action, and handling that action in `router.getStateForAction`.

### Navigation State

Expand Down Expand Up @@ -74,7 +74,7 @@ To help developers implement custom navigators, the following utilities are prov

### `createNavigator`

This utility combines a [router](/docs/routers/) and a [navigation view](/docs/navigation-views/) together in a standard way:
This utility combines a [router](/docs/routers) and a [navigation view](/docs/navigation-views) together in a standard way:

```js
const MyApp = createNavigator(MyRouter)(MyView);
Expand Down