testing-library · alexkrolick · Nov 4, 2020 · Sep 12, 2020 · Sep 12, 2020 · Sep 12, 2020
diff --git a/.gitignore b/.gitignore
@@ -10,6 +10,9 @@ website/build/
 website/yarn.lock
 website/node_modules
 website/i18n/*
+website/.docusaurus
+website/.cache-loader
+website-old
 
 *.log
 

diff --git a/docs/dom-testing-library/api-async.md b/docs/dom-testing-library/api-async.md
@@ -51,7 +51,7 @@ The default `onTimeout` takes the error and appends the `container`'s printed
 state to the error message which should hopefully make it easier to track down
 what caused the timeout.
 
-<a name="mutationobserveroptions"></a>The default `mutationObserverOptions` is
+The default `mutationObserverOptions` is
 `{subtree: true, childList: true, attributes: true, characterData: true}` which
 will detect additions and removals of child elements (including text nodes) in
 the `container` and any of its descendants. It will also detect attribute
@@ -99,14 +99,14 @@ el.parentElement.removeChild(el)
 or an empty array:
 
 ```javascript
-waitForElementToBeRemoved(null).catch(err => console.log(err))
-waitForElementToBeRemoved(queryByText(/not here/i)).catch(err =>
+waitForElementToBeRemoved(null).catch((err) => console.log(err))
+waitForElementToBeRemoved(queryByText(/not here/i)).catch((err) =>
   console.log(err)
 )
-waitForElementToBeRemoved(queryAllByText(/not here/i)).catch(err =>
+waitForElementToBeRemoved(queryAllByText(/not here/i)).catch((err) =>
   console.log(err)
 )
-waitForElementToBeRemoved(() => getByText(/not here/i)).catch(err =>
+waitForElementToBeRemoved(() => getByText(/not here/i)).catch((err) =>
   console.log(err)
 )
 
@@ -158,7 +158,7 @@ changed:
 const container = document.createElement('div')
 waitForDomChange({ container })
   .then(() => console.log('DOM changed!'))
-  .catch(err => console.log(`Error you need to deal with: ${err}`))
+  .catch((err) => console.log(`Error you need to deal with: ${err}`))
 container.append(document.createElement('p'))
 // if 👆 was the only code affecting the container and it was not run,
 // waitForDomChange would throw an error
@@ -172,7 +172,7 @@ container
 ```javascript
 const container = document.createElement('div')
 container.setAttribute('data-cool', 'true')
-waitForDomChange({ container }).then(mutationsList => {
+waitForDomChange({ container }).then((mutationsList) => {
   const mutation = mutationsList[0]
   console.log(
     `was cool: ${mutation.oldValue}\ncurrently cool: ${mutation.target.dataset.cool}`
@@ -192,7 +192,7 @@ wait for are descendants of `container`.
 The default `timeout` is `1000ms` which will keep you under
 [Jest's default timeout of `5000ms`](https://jestjs.io/docs/en/jest-object.html#jestsettimeouttimeout).
 
-<a name="mutationobserveroptions"></a>The default `mutationObserverOptions` is
+The default `mutationObserverOptions` is
 `{subtree: true, childList: true, attributes: true, characterData: true}` which
 will detect additions and removals of child elements (including text nodes) in
 the `container` and any of its descendants. It will also detect attribute
@@ -251,7 +251,7 @@ wait for will be attached to it, or set a different `container`.
 The default `timeout` is `4500ms` which will keep you under
 [Jest's default timeout of `5000ms`](https://facebook.github.io/jest/docs/en/jest-object.html#jestsettimeouttimeout).
 
-<a name="mutationobserveroptions"></a>The default `mutationObserverOptions` is
+The default `mutationObserverOptions` is
 `{subtree: true, childList: true, attributes: true, characterData: true}` which
 will detect additions and removals of child elements (including text nodes) in
 the `container` and any of its descendants. It will also detect attribute

diff --git a/docs/dom-testing-library/faq.md b/docs/dom-testing-library/faq.md
@@ -106,9 +106,9 @@ Please refer to the [Guiding Principles](../guiding-principles) of this testing
 library for more info.
 
 </details>
-<!--
-Links:
--->
+
+<!-- Links: -->
+
 
 <!-- prettier-ignore-start -->
 

diff --git a/docs/example-codesandbox.md b/docs/example-codesandbox.md
@@ -8,7 +8,7 @@ You can find runnable examples for many common use cases on Codesandbox.
 
 [![Open react-testing-library-examples](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/github/kentcdodds/react-testing-library-examples/tree/master/)
 
-<iframe src="https://codesandbox.io/embed/github/kentcdodds/react-testing-library-examples/tree/master/?expanddevtools=1&fontsize=13&hidenavigation=1&initialpath=%2F__tests__%2Fasync.js&module=%2Fsrc%2F__tests__%2Fasync.js&moduleview=1&previewwindow=tests&view=editor" style="width:100%; height:500px; border:0; border-radius: 4px; overflow:hidden;" sandbox="allow-modals allow-forms allow-popups allow-scripts allow-same-origin"></iframe>
+<iframe src="https://codesandbox.io/embed/github/kentcdodds/react-testing-library-examples/tree/master/?expanddevtools=1&fontsize=13&hidenavigation=1&initialpath=%2F__tests__%2Fasync.js&module=%2Fsrc%2F__tests__%2Fasync.js&moduleview=1&previewwindow=tests&view=editor" style={{width: '100%', height:500, border:0, borderRadius: 4, overflow:'hidden'}} sandbox="allow-modals allow-forms allow-popups allow-scripts allow-same-origin"></iframe>
 
 ## Playground
 

diff --git a/docs/example-external.md b/docs/example-external.md
@@ -20,5 +20,5 @@ sidebar_label: External Examples
   Tolinski
 
 <a href="https://youtu.be/JKOwJUM4_RM">
-  <img width="200px" alt="what is react testing library" src='https://img.youtube.com/vi/JKOwJUM4_RM/0.jpg' style="margin-left: 36px" />
+  <img width="200px" alt="what is react testing library" src='https://img.youtube.com/vi/JKOwJUM4_RM/0.jpg' style={{marginLeft: 36}} />
 </a>
diff --git a/docs/intro.md b/docs/intro.md
@@ -1,6 +1,7 @@
 ---
 id: intro
 title: Introduction
+slug: /
 ---
 
 The [`@testing-library`][npm] family of packages helps you test UI components in
@@ -45,7 +46,8 @@ Testing Library encourages you to avoid testing
 [implementation details](https://kentcdodds.com/blog/testing-implementation-details)
 like the internals of a component you're testing (though it's still possible).
 [The Guiding Principles](/docs/guiding-principles) of this library emphasize a
-focus on tests that closely resemble how your web pages are interacted by the users.
+focus on tests that closely resemble how your web pages are interacted by the
+users.
 
 You may want to avoid following implementation details:
 

diff --git a/docs/marko-testing-library/api.md b/docs/marko-testing-library/api.md
@@ -7,6 +7,14 @@ title: API
 as these methods:
 
 - [`render`](#render)
+  - [`render` Options](#render-options)
+    - [`container`](#container)
+- [`render` Result](#render-result)
+  - [`...queries`](#queries)
+  - [`debug`](#debug)
+  - [`rerender`](#rerender)
+  - [`emitted`](#emitted)
+  - [`container`](#container-1)
 - [`cleanup`](#cleanup)
 
 ---
@@ -207,8 +215,9 @@ expect(emitted()).toMatchInlineSnapshot(`
 ### `container`
 
 The containing DOM node of your rendered Marko Component. For server side tests
-this is a [JSDOM.fragment](), and for client side tests this will be whatever is
-passed as the `container` render option.
+this is a [JSDOM.fragment](https://github.com/jsdom/jsdom#fragment), and for
+client side tests this will be whatever is passed as the `container` render
+option.
 
 > Tip: To get the root element of your rendered element, use
 > `container.firstChild`.

diff --git a/docs/react-native-testing-library/setup.md b/docs/react-native-testing-library/setup.md
@@ -21,9 +21,6 @@ with this file in all your imports. See
 [below](#configuring-jest-with-test-utils) for a way to make your test util file
 accessible without using relative paths.
 
-The example below sets up data providers using the
-[`wrapper`](api-render.md#render-options) option to `render`.
-
 ```diff
 // my-component.test.js
 - import { render, fireEvent } from '@testing-library/react-native';

diff --git a/docs/react-testing-library/intro.md b/docs/react-testing-library/intro.md
@@ -74,7 +74,7 @@ Have a look at the "What is React Testing library?" video below for an
 introduction to the library.
 
 <a href="https://youtu.be/JKOwJUM4_RM">
-  <img width="200px" alt="what is react testing library" src='https://img.youtube.com/vi/JKOwJUM4_RM/0.jpg' style="margin-left: 0" />
+  <img width="200px" alt="what is react testing library" src='https://img.youtube.com/vi/JKOwJUM4_RM/0.jpg' style={{marginLeft: 0}} />
 </a>
 
 Also, don't miss this

diff --git a/docs/react-testing-library/setup.md b/docs/react-testing-library/setup.md
@@ -69,7 +69,6 @@ export { customRender as render }
 > [#169](https://github.com/testing-library/react-testing-library/issues/169)
 > and the workaround below.
 
-<details>
 <summary>Workaround for Babel 6</summary>
 
 You can use CommonJS modules instead of ES modules, which should work in Node:
@@ -90,8 +89,6 @@ module.exports = {
 }
 ```
 
-</details>
-
 ### Add custom queries
 
 > **Note**
@@ -175,8 +172,6 @@ const { getByDataCy } = render(<Component />)
 expect(getByDataCy('my-component')).toHaveTextContent('Hello')
 ```
 
-</details>
-
 ### Configuring Jest with Test Utils
 
 To make your custom test file accessible in your Jest test files without using

diff --git a/netlify.toml b/netlify.toml
@@ -8,7 +8,7 @@
   # Directory (relative to root of your repo) that contains the deploy-ready
   # HTML files and assets generated by the build. If a base directory has
   # been specified, include it in the publish directory path.
-  publish = "website/build/testing-library-docs"
+  publish = "website/build"
 
   # Default build command.
   command = "cd website; npm install; npm run format-docs; npm run build"