docs: fix broken links (#680)

Author: MatanBobi

docs/dom-testing-library/api-configuration.mdx

@@ -29,7 +29,7 @@ e.g. `window.getComputedStyle(document.createElement('div'), '::after')`.
 Defaults to `false`
 
 `defaultHidden`: The default value for the `hidden` option used by
-[`getByRole`](api-queries#byrole). Defaults to `false`.
+[`getByRole`](api-queries.mdx#byrole). Defaults to `false`.
 
 `showOriginalStackTrace`: By default, `waitFor` will ensure that the stack trace
 for errors thrown by Testing Library is cleaned up and shortened so it's easier
@@ -50,11 +50,11 @@ option.
 screen.getByTestId('foo', { suggest: false }) // will not throw a suggestion
 ```
 
-`testIdAttribute`: The attribute used by [`getByTestId`](api-queries#bytestid)
+`testIdAttribute`: The attribute used by [`getByTestId`](api-queries.mdx#bytestid)
 and related queries. Defaults to `data-testid`.
 
 `getElementError`: A function that returns the error used when
-[`getBy*`](api-queries#getby) or [`getAllBy*`](api-queries#getallby) fail. Takes
+[`getBy*`](api-queries.mdx#getby) or [`getAllBy*`](api-queries.mdx#getallby) fail. Takes
 the error message and container object as arguments.
 
 `asyncUtilTimeout`: The global timeout value in milliseconds used by `waitFor`

docs/dom-testing-library/api-helpers.mdx

@@ -61,15 +61,15 @@ module.exports = {
 >
 > Custom queries can be added to `React Testing Library`'s `render` method by
 > adding `queries` to the options config object. See the render
-> [options](/docs/react-testing-library/api#render-options).
+> [options](react-testing-library/api.mdx#render-options).
 
 ## `buildQueries`
 
 The `buildQueries` helper allows you to create custom queries with all standard
 [variants](api-queries.mdx) of queries in testing-library.
 
 See the
-[Add custom queries](/docs/react-testing-library/setup#add-custom-queries)
+[Add custom queries](react-testing-library/setup.mdx#add-custom-queries)
 section of the custom render guide for example usage.
 
 ### Using other assertion libraries

docs/dom-testing-library/api-queries.mdx

@@ -43,7 +43,7 @@ to find more than one element, then use `findAllBy`.
 > **Note**
 >
 > this is a simple combination of `getBy*` queries and
-> [`waitFor`](api-async#waitfor). The `findBy*` queries accept the `waitFor`
+> [`waitFor`](api-async.mdx#waitfor). The `findBy*` queries accept the `waitFor`
 > options as the last argument. (i.e.
 > `screen.findByText('text', queryOptions, waitForOptions)`)
 
@@ -708,7 +708,7 @@ assertions about the `Open dialog`-button you would need to use
 `getAllByRole('button', { hidden: true })`.
 
 The default value for `hidden` can
-[be configured](api-configuration#configuration).
+[be configured](api-configuration.mdx#configuration).
 
 #### `selected`
 

docs/dom-testing-library/faq.mdx

@@ -102,7 +102,7 @@ details** of the component.
 
 We believe this leads to less brittle and more meaningful test code.
 
-Please refer to the [Guiding Principles](../guiding-principles) of this testing
+Please refer to the [Guiding Principles](guiding-principles.mdx) of this testing
 library for more info.
 
 </details>

docs/ecosystem-bs-jest-dom.mdx

@@ -4,7 +4,7 @@ title: bs-jest-dom
 ---
 
 [`bs-jest-dom`][gh] is a companion library for
-[`bs-react-testing-library`](/docs/bs-react-testing-library/intro) that provides
+[`bs-react-testing-library`](bs-react-testing-library/intro.mdx) that provides
 custom DOM element matchers for Jest in [ReasonML][re] via
 [BuckleScript][bucklescript].
 

docs/example-react-intl.mdx

@@ -76,7 +76,7 @@ You have two options:
 
 To test our translated component we can create a custom `render` function using
 the `wrapper` option as explained in the
-[setup](./react-testing-library/setup.mdx) page. 
+[setup](react-testing-library/setup.mdx) page. 
 Our custom `render` function can look like this:
 
 ```jsx

docs/marko-testing-library/intro.mdx

@@ -49,8 +49,8 @@ when a real user uses it.
 **What this library is not**:
 
 1. A test runner or framework
-2. Specific to a testing framework, you can [use it with Jest](./setup#jest),
- [mocha](./setup#mocha), or other test runners.
+2. Specific to a testing framework, you can [use it with Jest](setup.mdx#jest),
+ [mocha](setup.mdx#mocha), or other test runners.
 
 > NOTE: This library is built on top of
 > [`DOM Testing Library`](dom-testing-library/intro.mdx) which is where most of

docs/nightwatch-testing-library/intro.mdx

@@ -136,5 +136,5 @@ module.exports = {
 }
 ```
 
-[config]: https://testing-library.com/docs/dom-testing-library/api-configuration
+[config]: ../dom-testing-library/api-configuration.mdx
 [gh]: https://github.com/testing-library/nightwatch-testing-library

docs/preact-testing-library/api.mdx

@@ -16,7 +16,7 @@ sidebar_label: API
 
 This library re-exports everything from the DOM Testing Library
 (`@testing-library/dom`). See the
-[documentation](../dom-testing-library/api-queries.mdx) to see what goodies you
+[documentation](dom-testing-library/api-queries.mdx) to see what goodies you
 can use.
 
 ## `render`
@@ -33,7 +33,7 @@ const { results } = render(<YourComponent />, { options })
 | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- |
 | `container` | The HTML element the component is mounted to. | baseElement |
 | `baseElement` | The root HTML element to which the container is appended to. | document.body |
-| `queries` | Queries to bind to the baseElement. See [getQueriesForElement](../dom-testing-library/api-helpers#within-and-getqueriesforelement-apis). | null |
+| `queries` | Queries to bind to the baseElement. See [getQueriesForElement](dom-testing-library/api-helpers.mdx#within-and-getqueriesforelement-apis). | null |
 | `hydrate` | Used when the component has already been mounted and requires a rerender. Not needed for most people. The rerender function passed back to you does this already. | false |
 | `wrapper` | A parent component to wrap YourComponent. | null |
 
@@ -43,11 +43,11 @@ const { results } = render(<YourComponent />, { options })
 | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `container` | The HTML element the component is mounted to. |
 | `baseElement` | The root HTML element to which the container is appended to. |
-| `debug` | Logs the baseElement using [prettyDom](https://testing-library.com/docs/dom-testing-library/api-helpers#prettydom). |
+| `debug` | Logs the baseElement using [prettyDom](dom-testing-library/api-helpers.mdx#prettydom). |
 | `unmount` | Unmounts the component from the container. |
 | `rerender` | Calls render again passing in the original arguments and sets hydrate to true. |
 | `asFragment` | Returns the innerHTML of the container. |
-| `...queries` | Returns all [query functions](https://testing-library.com/docs/dom-testing-library/api-queries) to be used on the baseElement. If you pass in `query` arguments than this will be those, otherwise all. |
+| `...queries` | Returns all [query functions](dom-testing-library/api-queries.mdx) to be used on the baseElement. If you pass in `query` arguments than this will be those, otherwise all. |
 
 ## `cleanup`
 
@@ -82,7 +82,7 @@ Even thought it's for React, it gives you an idea of why it's needed.
 ## `fireEvent`
 
 Passes it to the @testing-library/dom
-[fireEvent](../dom-testing-library/api-events). It's also wrapped in `act` so
+[fireEvent](dom-testing-library/api-events.mdx). It's also wrapped in `act` so
 you don't need to worry about doing it.
 
 📝 Keep in mind mainly when using `h / Preact.createElement` that React uses a

docs/preact-testing-library/intro.mdx

@@ -34,13 +34,13 @@ See the [Dom introduction][dom-solution-explainer] and [React
 introduction][react-solution-explainer] for a more in-depth explanation.
 
 [dom-solution-explainer]: ../dom-testing-library/intro.mdx#this-solution
-[react-solution-explainer]: ../react-testing-library/intro#this-solution
+[react-solution-explainer]: ../react-testing-library/intro.mdx#this-solution
 
 **What this library is not**:
 
 1. A test runner or framework.
 2. Specific to a testing framework.
 
 We recommend Jest as our preference. You can checkout
-[Using Without Jest](../react-testing-library/setup#using-without-jest) if
+[Using Without Jest](react-testing-library/setup.mdx#using-without-jest) if
 you're looking to use another framework.