Skip to content

Commit 0a7bf61

Browse files
committed
Fix outdated info about navigate
1 parent 01b9a1a commit 0a7bf61

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

versioned_docs/version-7.x/navigating.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -216,7 +216,7 @@ export default function App() {
216216
<source src="/assets/navigators/stack/stack-push.mp4" />
217217
</video>
218218

219-
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.
220220

221221
## Going back
222222

@@ -358,7 +358,7 @@ export default function App() {
358358

359359
## Summary
360360

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.
362362
- We can call `navigation.push('RouteName')` as many times as we like and it will continue pushing routes.
363363
- 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.
364364
- 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

Comments
 (0)