Skip to content

Commit f1ab2bc

Browse files
committed
Fix popTo description
1 parent db23292 commit f1ab2bc

File tree

2 files changed

+1
-4
lines changed

2 files changed

+1
-4
lines changed

versioned_docs/version-7.x/stack-navigator.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -585,9 +585,6 @@ navigation.pop();
585585

586586
Navigates back to a previous screen in the stack by popping screens after it. The method accepts the following arguments:
587587

588-
- `name` - _string_ - Name of the route to navigate to.
589-
- `params` - _object_ - Screen params to pass to the destination route.
590-
591588
- `name` - _string_ - Name of the route to navigate to.
592589
- `params` - _object_ - Screen params to pass to the destination route.
593590
- `merge` - _boolean_ - Whether params should be merged with the existing route params, or replace them (when navigating to an existing screen). Defaults to `false`.

versioned_docs/version-7.x/troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -257,7 +257,7 @@ This can happen if you are passing non-serializable values such as class instanc
257257
Example of some use cases for passing functions in params are the following:
258258
259259
- To pass a callback to use in a header button. This can be achieved using `navigation.setOptions` instead. See the [guide for header buttons](header-buttons.md#header-interaction-with-its-screen-component) for examples.
260-
- To pass a callback to the next screen which it can call to pass some data back. You can usually achieve it using `navigate` instead. See the [guide for params](params.md) for examples.
260+
- To pass a callback to the next screen which it can call to pass some data back. You can usually achieve it using `popTo` instead. See [passing params to a previous screen](params.md#passing-params-to-a-previous-screen) for examples.
261261
- To pass complex data to another screen. Instead of passing the data `params`, you can store that complex data somewhere else (like a global store), and pass an id instead. Then the screen can get the data from the global store using the id. See [what should be in params](params.md#what-should-be-in-params).
262262
- Pass data, callbacks etc. from a parent to child screens. You can either use React Context, or pass a children callback to pass these down instead of using params. See [passing additional props](hello-react-navigation.md#passing-additional-props).
263263

0 commit comments

Comments
 (0)