Skip to content

Commit 19ceb00

Browse files
committed
Remove section with incorrect description of preload
1 parent 2d57ccb commit 19ceb00

1 file changed

Lines changed: 0 additions & 14 deletions

File tree

versioned_docs/version-8.x/upgrading-from-7.x.md

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -342,20 +342,6 @@ If you use a custom navigator with `StackRouter` and do not want to change the s
342342

343343
See [Navigation state](navigation-state.md) for more details.
344344

345-
##### `preload` reuses matching preloaded routes instead of adding new ones
346-
347-
Previously, calling `preload` for the same screen multiple times in a Stack or Native Stack Navigator would always preload a new instance of screen, leading to multiple preloaded instances. We found that this behavior was not intuitive and most people expected to have a single instance.
348-
349-
In React Navigation 8, calling `preload` for a matching preloaded screen updates its params instead of adding another preloaded screen:
350-
351-
```js
352-
navigation.preload('Profile', { user: 'jane' });
353-
```
354-
355-
By default, preloaded screens are matched based on the screen name. The [`getId`](screen.md#id) prop can be used to match based on an ID derived from the params instead.
356-
357-
See [`preload`](navigation-actions.md#preload) for more details.
358-
359345
##### Preloaded screens behave closer to regular screens
360346

361347
Previously, when a screen was preloaded in Stack and Native Stack Navigators, there were a few restrictions:

0 commit comments

Comments
 (0)