From 7337a3ff65565fa173ddd64f3ae0cd1ed25af600 Mon Sep 17 00:00:00 2001 From: Vojtech Novak Date: Tue, 13 Mar 2018 20:05:14 +0100 Subject: [PATCH] Update custom-navigators.md --- docs/custom-navigators.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/custom-navigators.md b/docs/custom-navigators.md index d22672c8b9..f11f69b740 100644 --- a/docs/custom-navigators.md +++ b/docs/custom-navigators.md @@ -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 @@ -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);