From 7fe76fb7c65a14cf50154ea87a5f02081fdd4425 Mon Sep 17 00:00:00 2001 From: Nicolas Charpentier Date: Sat, 16 Dec 2017 14:17:43 -0500 Subject: [PATCH] Fix handling the Hardware Back Button link in Redux section (#3134) --- docs/guides/Redux-Integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/Redux-Integration.md b/docs/guides/Redux-Integration.md index 0cd6bfe9b5..d1db71b1fd 100644 --- a/docs/guides/Redux-Integration.md +++ b/docs/guides/Redux-Integration.md @@ -61,7 +61,7 @@ class Root extends React.Component { Once you do this, your navigation state is stored within your redux store, at which point you can fire navigation actions using your redux dispatch function. -Keep in mind that when a navigator is given a `navigation` prop, it relinquishes control of its internal state. That means you are now responsible for persisting its state, handling any deep linking, [Handling the Hardware Back Button in Android](#handling-the-hardware-back-button-in-android), etc. +Keep in mind that when a navigator is given a `navigation` prop, it relinquishes control of its internal state. That means you are now responsible for persisting its state, handling any deep linking, [Handling the Hardware Back Button in Android](#Handling-the-Hardware-Back-Button-in-Android), etc. Navigation state is automatically passed down from one navigator to another when you nest them. Note that in order for a child navigator to receive the state from a parent navigator, it should be defined as a `screen`.