[router] rework unstable_settings.initialRouteName to unstable_settings.anchor #28644
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.
Why
During normal navigation, the target screen will the initial route of a navigator. React Navigation allows users to disable this behaviour (via the
initial: false
option when dispatching a navigation event). When disabled, the navigator determines the index of the target route (e.g it might have aninitialRouteName
which will be used as the initial route).I'm adding this as a feature, as it has both been requested and also is a stumbling block for new users.
How
initial={Boolean}
prop to<Link />
router.{navigate,push,replace}()
now accepts a second options argument. The only option is{ initialScreen: Boolean }
Test Plan
Updated unit tests
Checklist
npx expo prebuild
& EAS Build (eg: updated a module plugin).