-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Navigator: fix isInitial, refine focusSelector logic #64786
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
09b48d6
Fix isInitial logic
ciampo bfaccad
Use '@wordpress/warning' instead of console.warn
ciampo 3e6dcbd
Improved destructuring and isInitial assignment
ciampo fe16bbf
Refactor focus selector logic, better cleanup, lazier map copy
ciampo c8a3f44
Remove unnecessary optional chaining — currentLocation is always defined
ciampo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
If I'm at initial location
/foo
and callgoTo( '/foo' )
, it will reset theisInitial
flag and that's all. Isn't it going to fire an animation? Like the same UI sliding from right "into itself"?By the way, all the
?.path
optional chainings are not needed,.path
is enough.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.
I don't think "to same screen" navigations have ever been supported — for the animation to work, we'd need to create a clone of the current screen to transition to.
This is true also for "parametrised" screens. For example, if we have a
<Navigator.Screen path="/product/:id" />
, navigating from/product/1
toproduct/2
won't currently trigger an animation.I don't think this has ever been a requirement, and that's why it's not supported.
Good point, I pushed a commit removing those optional chainings