feat(react-navigation): add Detour linking adapter API and migrate examples to linking-based integration - #63
Merged
Conversation
BrtqKr
approved these changes
May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a dedicated React Navigation adapter API to Detour and updates both React Navigation examples to use linking-based flows aligned with React Navigation docs.
Changes
Detour.getInitialURL,Detour.addEventListener,DETOUR_LINKING_PREFIX).getInitialURL+subscribelinking flow.react-navigationexample to use this adapter inline with a declarativelinkingConfig.react-navigation-advancedexample to use the same inline adapter pattern, combined with conditional screen rendering andUNSTABLE_routeNamesChangeBehavior="lastUnhandled"so React Navigation natively replays deep links across the sign-in → onboarding gate.