Document that deep links are enabled by default in static config

Author: satya164

versioned_docs/version-8.x/configuring-links.md

@@ -18,19 +18,59 @@ Make sure that you have [configured deep links](deep-linking.md) in your app bef
 <Tabs groupId="config" queryString="config">
 <TabItem value="static" label="Static" default>
 
-The [`Navigation`](static-configuration.md#createstaticnavigation) component accepts a [`linking`](static-configuration.md#differences-in-the-linking-prop) prop that makes it easier to handle incoming links:
+React Navigation handles incoming links by default when using [static configuration](static-configuration.md). All leaf screens in the navigator will be assigned a path based on their name automatically. No additional configuration is necessary.
+
+This is equivalent to specifying [`linking`](navigation-container.md#linking) prop on [`Navigation`](static-configuration.md#createstaticnavigation) with `enabled: 'auto'`.
+
+</TabItem>
+<TabItem value="dynamic" label="Dynamic">
+
+The [`NavigationContainer`](navigation-container.md) component accepts a [`linking`](navigation-container.md#linking) prop that makes it easier to handle incoming links.
+
+The `config` option in the `linking` prop lets you specify how paths map to screens in your navigation structure:
+
+```js
+import { NavigationContainer } from '@react-navigation/native';
+
+// highlight-start
+const linking = {
+  config: {
+    /* configuration for matching screens with paths */
+  },
+};
+// highlight-end
+
+function App() {
+  return (
+    <NavigationContainer
+      // highlight-next-line
+      linking={linking}
+    >
+      {/* content */}
+    </NavigationContainer>
+  );
+}
+```
+
+When you specify the `linking` prop, React Navigation will handle incoming links automatically.
+
+</TabItem>
+</Tabs>
+
+On Android and iOS, it'll use React Native's [`Linking` module](https://reactnative.dev/docs/linking) to handle incoming deep links and universal links. On the Web, it'll use the [History API](https://developer.mozilla.org/en-US/docs/Web/API/History_API) to sync the URL with the browser.
+
+You can also pass a [`fallback`](navigation-container.md#fallback) prop that controls what's displayed when React Navigation is trying to resolve the initial deep link URL:
+
+<Tabs groupId="config" queryString="config">
+<TabItem value="static" label="Static" default>
 
 ```js
 import { createStaticNavigation } from '@react-navigation/native';
 
 function App() {
   return (
     <Navigation
-      // highlight-start
-      linking={{
-        enabled: 'auto',
-      }}
-      // highlight-end
+      // highlight-next-line
       fallback={<Text>Loading...</Text>}
     />
   );
@@ -42,24 +82,18 @@ const Navigation = createStaticNavigation(RootStack);
 </TabItem>
 <TabItem value="dynamic" label="Dynamic">
 
-The `NavigationContainer` accepts a [`linking`](navigation-container.md#linking) prop that makes it easier to handle incoming links. The 2 of the most important properties you can specify in the `linking` prop are `prefixes` and `config`:
-
 ```js
 import { NavigationContainer } from '@react-navigation/native';
 
-// highlight-start
 const linking = {
-  config: {
-    /* configuration for matching screens with paths */
-  },
+  // ...
 };
-// highlight-end
 
 function App() {
   return (
     <NavigationContainer
-      // highlight-next-line
       linking={linking}
+      // highlight-next-line
       fallback={<Text>Loading...</Text>}
     >
       {/* content */}
@@ -71,11 +105,7 @@ function App() {
 </TabItem>
 </Tabs>
 
-When you specify the `linking` prop, React Navigation will handle incoming links automatically.
-
-On Android and iOS, it'll use React Native's [`Linking` module](https://reactnative.dev/docs/linking) to handle incoming deep links and universal links, both when the app was opened with the link, and when new links are received when the app is open. On the Web, it'll use the [History API](https://developer.mozilla.org/en-US/docs/Web/API/History_API) to sync the URL with the browser.
-
-You can also pass a [`fallback`](navigation-container.md#fallback) prop that controls what's displayed when React Navigation is trying to resolve the initial deep link URL.
+The behavior can be customized further by specifying additional options in the `linking` prop as described below.
 
 ## Prefixes
 

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

@@ -264,6 +264,8 @@ Similar to `NavigationContainer`, the component returned by `createStaticNavigat
 
    See [How does automatic path generation work](configuring-links.md#how-does-automatic-path-generation-work) for more details.
 
+By default, linking is enabled in static configuration with automatic path generation. It needs to be explicitly disabled by passing `enabled: false` to the `linking` prop if you don't want linking support.
+
 ## `createComponentForStaticNavigation`
 
 The `createComponentForStaticNavigation` function takes the static config returned by `createXNavigator` functions and returns a React component to render. The second argument is a name for the component that'd be used in React DevTools:

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

@@ -565,6 +565,22 @@ The `prefixes` default to `['*']`, which will match any host starting with `http
 
 See [Configuring links](configuring-links.md) for more details.
 
+#### Deep links are now enabled by default in Static Configuration
+
+Previously, deep linking needs to be explicitly enabled by setting `linking.enabled` to `auto` or by passing a `linking` prop. The additional step was necessary since we also needed `prefixes` to be specified in the linking config.
+
+In React Navigation 8, it now defaults to `auto`, so deep linking is enabled by default with automatic path generation based on screen names when using static configuration:
+
+If you don't want to enable deep linking, you can set `linking.enabled` to `false`:
+
+```diff lang=js
+<Navigation
++   linking={{
++     enabled: false,
++   }}
+>
+```
+
 #### Some exports are removed from `@react-navigation/elements`
 
 The `@react-navigation/elements` package has exported some components that were primarily intended for internal usage. These components have been removed from the public API: