Skip to content

Commit 1abf318

Browse files
committed
Add a note about linking.enabled: true to static config docs
1 parent 3830698 commit 1abf318

2 files changed

Lines changed: 4 additions & 0 deletions

File tree

versioned_docs/version-7.x/static-configuration.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -383,6 +383,8 @@ Similar to `NavigationContainer`, the component returned by `createStaticNavigat
383383

384384
See [How does automatic path generation work](configuring-links.md#how-does-automatic-path-generation-work) for more details.
385385

386+
Passing `enabled: true` enables linking support without automatic path generation, which means only the paths specified in the [screen's `linking` configuration](#linking) explicitly will be used for deep linking.
387+
386388
## `createPathConfigForStaticNavigation`
387389

388390
The `createPathConfigForStaticNavigation` function takes the static config returned by `createXNavigator` functions and returns a path config object that can be used within the linking config.

versioned_docs/version-8.x/static-configuration.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -383,3 +383,5 @@ Similar to `NavigationContainer`, the component returned by `createStaticNavigat
383383
See [How does automatic path generation work](configuring-links.md#how-does-automatic-path-generation-work) for more details.
384384

385385
By default, linking is enabled in static configuration with automatic path generation. If you don't want linking support, it can be disabled by explicitly passing `enabled: false` to the `linking` prop.
386+
387+
Passing `enabled: true` enables linking support without automatic path generation, which means only the paths specified in the [screen's `linking` configuration](#linking) explicitly will be used for deep linking.

0 commit comments

Comments
 (0)