Fix broken anchor links

Author: satya164

blog/2020-02-06-react-navigation-5.0.md

@@ -53,7 +53,7 @@ Hooks are great for stateful logic and code organization. Now we have several ho
 
 ### Update options from component
 
-We’ve added a new [`setOptions`](/docs/5.x/navigation-prop#setoptions---update-screen-options-from-the-component) method on the `navigation` prop to make configuring screen navigation options more intuitive than its `static navigationOptions` predecessor. It lets us **easily set screen options based on props, state or context without messing with params**. Instead of using static options, we can call it anytime to configure the screen.
+We’ve added a new [`setOptions`](/docs/5.x/navigation-prop#setoptions) method on the `navigation` prop to make configuring screen navigation options more intuitive than its `static navigationOptions` predecessor. It lets us **easily set screen options based on props, state or context without messing with params**. Instead of using static options, we can call it anytime to configure the screen.
 
 ```js
 navigation.setOptions({

docusaurus.config.js

@@ -12,6 +12,8 @@ export default {
   favicon: 'img/favicon.ico',
   organizationName: 'react-navigation',
   projectName: 'react-navigation.github.io',
+  onBrokenAnchors: 'throw',
+  onBrokenMarkdownLinks: 'throw',
   scripts: ['/js/snack-helpers.js', '/js/toc-fixes.js'],
   themeConfig: {
     colorMode: {

static/js/snack-helpers.js

@@ -184,24 +184,11 @@ function appendSnackLink() {
   });
 }
 
-// This is used to update links like the following:
-// [Full source of what we have built so far](#example/full-screen-modal)
-function transformExistingSnackLinks() {
-  document.querySelectorAll('a[href*="#example/"]').forEach((a) => {
-    let urlParts = a.href.split('#example/');
-    let templateId = urlParts[urlParts.length - 1];
-    a.href = getSnackUrl({ templateId });
-    a.target = '_blank';
-  });
-}
-
 function initializeSnackObservers() {
   appendSnackLink();
-  transformExistingSnackLinks();
 
   const mutationObserver = new MutationObserver((mutations) => {
     mutations.forEach(appendSnackLink);
-    mutations.forEach(transformExistingSnackLinks);
   });
 
   mutationObserver.observe(document.documentElement, {

versioned_docs/version-1.x/navigation-actions.md

@@ -13,15 +13,15 @@ The following actions are supported:
 - [Navigate](#navigate) - Navigate to another route
 - [Back](#back) - Go back to previous state
 - [Set Params](#setparams) - Set Params for given route
-- [Init](#init) - Used to initialize first state if state is undefined
+- Init - Used to initialize first state if state is undefined
 
 Within a stack, you can also use:
 
 - [Reset](#reset) - Replace current state with a new state
 - [Replace](#replace) - Replace a route at a given key with another route
-- [Push](#push) - Add a route on the top of the stack, and navigate forward to it
-- [Pop](#pop) - Navigate back to previous routes
-- [PopToTop](#poptotop) - Navigate to the top route of the stack, dismissing all other routes
+- Push - Add a route on the top of the stack, and navigate forward to it
+- Pop - Navigate back to previous routes
+- PopToTop - Navigate to the top route of the stack, dismissing all other routes
 
 The action creator functions define `toString()` to return the action type, which enables easy usage with third-party Redux libraries, including redux-actions and redux-saga.
 

versioned_docs/version-1.x/navigation-options.md

@@ -102,5 +102,5 @@ List of available navigation options depends on the `navigator` the screen is ad
 Check available options for:
 
 - [`drawer navigator`](drawer-navigator.md#screen-navigation-options)
-- [`stack navigator`](stack-navigator.md#screen-navigation-options)
-- [`tab navigator`](tab-navigator.md#screen-navigation-options)
+- [`stack navigator`](stack-navigator.md#navigationoptions-used-by-stacknavigator)
+- [`tab navigator`](tab-navigator.md#navigationoptions-used-by-tabnavigator)

versioned_docs/version-1.x/redux-integration.md

@@ -14,7 +14,7 @@ _You probably do not need to do this!_ Storing your React Navigation state in yo
 
 1. To handle your app's navigation state in Redux, you can pass your own `navigation` prop to a navigator.
 
-2. Once you pass your own navigation prop to the navigator, the default [`navigation`](navigation-prop.md) prop gets destroyed. You must construct your own `navigation` prop with [`state`](navigation-prop.md#state-the-screen-s-current-state-route), [`dispatch`](navigation-prop.md#dispatch-send-an-action-to-the-router), and `addListener` properties.
+2. Once you pass your own navigation prop to the navigator, the default [`navigation`](navigation-prop.md) prop gets destroyed. You must construct your own `navigation` prop with [`state`](navigation-prop.md#state---the-screens-current-stateroute), [`dispatch`](navigation-prop.md#dispatch---send-an-action-to-the-router), and `addListener` properties.
 
 3. The `state` will be fed from the reducer assigned to handle navigation state and the `dispatch` will be Redux's default `dispatch`. Thus you will be able to dispatch normal redux actions using `this.props.navigation.dispatch(ACTION)`, reducer will update the navigation state on the basis of dispatched action, the new navigation state will then be passed to the navigator.
 

versioned_docs/version-2.x/custom-android-back-button-handling.md

@@ -8,7 +8,7 @@ By default, when user presses the Android hardware back button, react-navigation
 
 > If you're looking for an easy-to-use solution, you can check out a community-developed package [react-navigation-backhandler](https://github.com/vonovak/react-navigation-backhandler). The following text shows what the package does under the cover.
 
-As an example, consider a screen where user is selecting items in a list, and a "selection mode" is active. On a back button press, you would first want the "selection mode" to be deactivated, and the screen should be popped only on the second back button press. The following code snippet demonstrates the situation. We make use of [`BackHandler`](https://reactnative.dev/docs/backhandler.html) which comes with react-native and we [subscribe to navigation lifecycle updates](navigation-prop.md#addlistener-subscribe-to-updates-to-navigation-lifecycle) to add our custom `hardwareBackPress` listener.
+As an example, consider a screen where user is selecting items in a list, and a "selection mode" is active. On a back button press, you would first want the "selection mode" to be deactivated, and the screen should be popped only on the second back button press. The following code snippet demonstrates the situation. We make use of [`BackHandler`](https://reactnative.dev/docs/backhandler.html) which comes with react-native and we [subscribe to navigation lifecycle updates](navigation-prop.md#addlistener---subscribe-to-updates-to-navigation-lifecycle) to add our custom `hardwareBackPress` listener.
 
 Returning `true` from `onBackButtonPressAndroid` denotes that we have handled the event, and react-navigation's listener will not get called, thus not popping the screen. Returning `false` will cause the event to bubble up and react-navigation's listener will pop the screen.
 

versioned_docs/version-2.x/custom-navigator-overview.md

@@ -24,7 +24,7 @@ The navigators render application screens which are just React components.
 To learn how to create screens, read about:
 
 - [Screen `navigation` prop](navigation-prop.md) to allow the screen to dispatch navigation actions, such as opening another screen
-- Screen `navigationOptions` to customize how the screen gets presented by the navigator (e.g. [header title](stack-navigator.md#navigationoptions-used-by-stacknavigator), tab label)
+- Screen `navigationOptions` to customize how the screen gets presented by the navigator (e.g. [header title](stack-navigator.md#navigationoptions-for-screens-inside-of-the-navigator), tab label)
 
 ### Calling Navigate on Top Level Component
 

versioned_docs/version-2.x/drawer-actions.md

@@ -8,9 +8,9 @@ sidebar_label: DrawerActions
 
 The following actions are supported:
 
-- [openDrawer](#openDrawer) - open the drawer
-- [closeDrawer](#closeDrawer) - close the drawer
-- [toggleDrawer](#toggleDrawer) - toggle the state, ie. switch from closed to open and vice versa
+- openDrawer - open the drawer
+- closeDrawer - close the drawer
+- toggleDrawer - toggle the state, ie. switch from closed to open and vice versa
 
 ### Usage
 

versioned_docs/version-2.x/headers.md

@@ -202,11 +202,11 @@ class HomeScreen extends React.Component {
 
 ## Additional configuration
 
-You can read the full list of available `navigationOptions` for screens inside of a stack navigator in the [`createStackNavigator` reference](stack-navigator.md#navigationoptions-used-by-stacknavigator).
+You can read the full list of available `navigationOptions` for screens inside of a stack navigator in the [`createStackNavigator` reference](stack-navigator.md#navigationoptions-for-screens-inside-of-the-navigator).
 
 ## Summary
 
-- You can customize the header inside of the `navigationOptions` static property on your screen components. Read the full list of options [in the API reference](stack-navigator.md#navigationoptions-used-by-stacknavigator).
+- You can customize the header inside of the `navigationOptions` static property on your screen components. Read the full list of options [in the API reference](stack-navigator.md#navigationoptions-for-screens-inside-of-the-navigator).
 - The `navigationOptions` static property can be an object or a function. When it is a function, it is provided with an object with the `navigation` prop, `screenProps`, and `navigationOptions` on it.
 - You can also specify shared `navigationOptions` in the stack navigator configuration when you initialize it. The static property takes precedence over that configuration.
 - [Full source of what we have built so far](https://snack.expo.io/@react-navigation/custom-header-title-component-v2).