refactor: upgrade nav dependencies #2408
Open
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
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
pwltr
force-pushed
the
chore/update-nav-deps
branch
from
161ca76 to
7bcaa3f
Compare
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@react-navigation/[email protected], npm/@react-navigation/[email protected], npm/@react-navigation/[email protected], npm/@react-navigation/[email protected], npm/@react-navigation/[email protected], npm/[email protected], npm/[email protected], npm/[email protected] |
pwltr
force-pushed
the
chore/update-nav-deps
branch
2 times, most recently
from
85ac376 to
e9b43bc
Compare
pwltr
changed the title
pwltr
force-pushed
the
chore/update-nav-deps
branch
from
e9b43bc to
c5c3e71
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Prerequisite for #2380
NavigationHeaderto always popTo() top most screen in the stackOpenConnectionSuccessFollow migration steps from https://reactnavigation.org/docs/upgrading-from-6.x:
<NavigationIndependentTree />popTo()for back navigationType of change
Tests
QA Notes
Make sure navigation, especially back and close buttons, works as expected.