Skip to content

Commit 2902f7c

Browse files
committed
docs: add dev-only warning explanation to README
1 parent 22dd4ce commit 2902f7c

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

examples/react-navigation-advanced/README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,12 @@ This example demonstrates an auth-gated React Navigation app with Detour integra
1818
- After sign-in, the rendered screen set changes. If onboarding has not been completed yet, `Onboarding` is shown — `Details` is still not rendered, so the pending link stays remembered.
1919
- After onboarding, `Details` becomes part of the rendered stack. React Navigation retries the unhandled action and navigates to `Details` (or falls through to `NotFound`).
2020

21+
### Expected dev-only warning
22+
23+
When the link arrives while the target screen isn't rendered yet (e.g. on `SignIn`), React Navigation logs a development-only warning.
24+
25+
This is the dispatch attempt against the current (signed-out) navigator state. `UNSTABLE_routeNamesChangeBehavior="lastUnhandled"` then stashes the action and replays it once `Details` is part of the rendered stack. The message is stripped in production builds.
26+
2127
Reference docs:
2228
- https://reactnavigation.org/docs/deep-linking?config=static#integrating-with-other-tools
2329
- https://reactnavigation.org/docs/auth-flow (see `UNSTABLE_routeNamesChangeBehavior`)

0 commit comments

Comments
 (0)