You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each time you call `push` we add a new route to the navigation stack. When you call `navigate` it first tries to find an existing route with that name, and only pushes a new route if there isn't yet one on the stack.
219
+
Each time you call `push` we add a new route to the navigation stack. When you call `navigate` it only pushes a new route if you're not already on that route.
220
220
221
221
## Going back
222
222
@@ -358,7 +358,7 @@ export default function App() {
358
358
359
359
## Summary
360
360
361
-
-`navigation.navigate('RouteName')` pushes a new route to the native stack navigator if it's not already in the stack, otherwise it jumps to that screen.
361
+
-`navigation.navigate('RouteName')` pushes a new route to the native stack navigator if you're not already on that route.
362
362
- We can call `navigation.push('RouteName')` as many times as we like and it will continue pushing routes.
363
363
- The header bar will automatically show a back button, but you can programmatically go back by calling `navigation.goBack()`. On Android, the hardware back button just works as expected.
364
364
- You can go back to an existing screen in the stack with `navigation.popTo('RouteName')`, and you can go back to the first screen in the stack with `navigation.popToTop()`.
0 commit comments