-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[router] rework unstable_settings.initialRouteName to unstable_settings.anchor #28644
Open
marklawlor
wants to merge
7
commits into
main
Choose a base branch
from
marklawlor/router/preverve-initial-screen
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
marklawlor
requested review from
Simek,
amandeepmittal and
EvanBacon
as code owners
May 6, 2024 20:50
expo-bot
added
bot: passed checks
ExpoBot has nothing to complain about
and removed
bot: suggestions
ExpoBot has some suggestions
labels
May 6, 2024
|
amandeepmittal
approved these changes
May 6, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm 👍
Left a couple of docs related suggestions.
marklawlor
changed the title
[router] add option to navigate to a route as a non-initial screen
[router] rework unstable_settings.initialRouteName to unstable_settings.anchor
May 8, 2024
marklawlor
force-pushed
the
marklawlor/router/preverve-initial-screen
branch
2 times, most recently
from
May 9, 2024 04:20
c591f81
to
7cfc92c
Compare
Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
Co-authored-by: Aman Mittal <amandeepmittal@live.com>
Co-authored-by: Aman Mittal <amandeepmittal@live.com>
marklawlor
force-pushed
the
marklawlor/router/preverve-initial-screen
branch
from
May 9, 2024 05:27
7cfc92c
to
5e8a665
Compare
EvanBacon
reviewed
May 9, 2024
@@ -44,4 +44,13 @@ export const unstable_settings = { | |||
}; | |||
``` | |||
|
|||
The `initialRouteName` is only used when deep-linking to a route. During app navigation, the route you are navigating to will be the initial route. You can disable this behavior using the `initial` prop on the `<Link />` component or by passing the option to the imperative APIs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should add a notice about this in the migration doc for React Navigation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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).