chore: format

Author: nickserv

docs/angular-testing-library/examples.mdx

@@ -57,11 +57,13 @@ describe('Counter', () => {
 
 ## With Standalone Components
 
-Angular Testing Library can also test your standalone components.
-In fact, it even becomes easier because you don't have to set up the whole Angular TestBed.
-This was previously only [possible when you used Single Component Angular Modules (SCAMs)](https://timdeschryver.dev/blog/single-component-angular-modules-and-component-tests-go-hand-in-hand).
+Angular Testing Library can also test your standalone components. In fact, it
+even becomes easier because you don't have to set up the whole Angular TestBed.
+This was previously only
+[possible when you used Single Component Angular Modules (SCAMs)](https://timdeschryver.dev/blog/single-component-angular-modules-and-component-tests-go-hand-in-hand).
 
-Let's migrate the counter component to a standalone component, and let's take a look at how this affects the test.
+Let's migrate the counter component to a standalone component, and let's take a
+look at how this affects the test.
 
 ```ts title="counter.component.ts"
 @Component({
@@ -86,8 +88,8 @@ export class CounterComponent {
 }
 ```
 
-Just as you would've expected, this doesn't affect the test cases.
-Writing tests for standalone components remains the same as for "regular" components.
+Just as you would've expected, this doesn't affect the test cases. Writing tests
+for standalone components remains the same as for "regular" components.
 
 ```ts title="counter.component.spec.ts"
 import {render, screen, fireEvent} from '@testing-library/angular'
@@ -114,7 +116,8 @@ describe('Counter', () => {
 })
 ```
 
-To override an import of a standalone component for your component test, you can use the [`componentImports` property](api.mdx#componentImports).
+To override an import of a standalone component for your component test, you can
+use the [`componentImports` property](api.mdx#componentImports).
 
 ## More examples
 
@@ -125,7 +128,9 @@ These examples include:
 - `@Input` and `@Output` properties
 - Forms
 - Integration with services
-- And [more](https://github.com/testing-library/angular-testing-library/tree/master/apps/example-app/src/app/examples)
+- And
+  [more](https://github.com/testing-library/angular-testing-library/tree/master/apps/example-app/src/app/examples)
 
 If you're looking for an example that isn't on the list, please feel free to
-create a [new issue](https://github.com/testing-library/angular-testing-library/issues/new).
+create a
+[new issue](https://github.com/testing-library/angular-testing-library/issues/new).

docs/angular-testing-library/faq.mdx

@@ -31,7 +31,8 @@ As you write your tests, keep in mind:
 
 In general, you should avoid mocking out components (see
 [the Guiding Principles section](guiding-principles.mdx)). However, if you need
-to, then try to use [ng-mocks](https://ng-mocks.sudo.eu/) and its [`MockBuilder`](https://ng-mocks.sudo.eu/extra/with-3rd-party#testing-libraryangular-and-mockbuilder).
+to, then try to use [ng-mocks](https://ng-mocks.sudo.eu/) and its
+[`MockBuilder`](https://ng-mocks.sudo.eu/extra/with-3rd-party#testing-libraryangular-and-mockbuilder).
 
 ```typescript
 import {Component, NgModule} from '@angular/core'
@@ -58,7 +59,7 @@ export class AppModule {}
 describe('ParentComponent', () => {
   it('should not render ChildComponent when shallow rendering', async () => {
     // all imports, declarations and exports of AppModule will be mocked.
-    const dependencies = MockBuilder(ParentComponent, AppModule).build();
+    const dependencies = MockBuilder(ParentComponent, AppModule).build()
 
     await render(ParentComponent, dependencies)
 

docs/angular-testing-library/version-compatibility.mdx

@@ -3,12 +3,12 @@ id: version-compatibility
 title: Version compatibility
 ---
 
-An overview of the compatibility between different versions of Angular Testing Library and Angular.
+An overview of the compatibility between different versions of Angular Testing
+Library and Angular.
 
 | Angular | Angular Testing Library |
 | ------- | ----------------------- |
 | 16.x    | 13.x \|\| 14.x          |
 | >= 15.1 | 13.x \|\| 14.x          |
 | < 15.1  | 11.x \|\| 12.x          |
 | 14.x    | 11.x \|\| 12.x          |
-

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

@@ -42,9 +42,9 @@ you'd like a solution that works for both, see
 
 **Note**: The output of the DOM is colorized by default if your tests are
 running in a node environment. However, you may sometimes want to turn off
-colors, such as in cases where the output is written to a log file for
-debugging purposes. You can use the environment variable `COLORS` to explicitly
-force the colorization off or on. For example:
+colors, such as in cases where the output is written to a log file for debugging
+purposes. You can use the environment variable `COLORS` to explicitly force the
+colorization off or on. For example:
 
 ```
 COLORS=false npm test
@@ -105,9 +105,9 @@ This function is what also powers
 
 ## `screen.debug()`
 
-For convenience `screen` also exposes a `debug` method.
-This method is essentially a shortcut for `console.log(prettyDOM())`. It
-supports debugging the document, a single element, or an array of elements.
+For convenience `screen` also exposes a `debug` method. This method is
+essentially a shortcut for `console.log(prettyDOM())`. It supports debugging the
+document, a single element, or an array of elements.
 
 ```javascript
 import {screen} from '@testing-library/dom'
@@ -129,8 +129,8 @@ screen.debug(screen.getAllByText('multi-test'))
 ## `screen.logTestingPlaygroundURL()`
 
 For debugging using [testing-playground](https://testing-playground.com), screen
-exposes this convenient method which logs and returns a URL that can be opened in
-a browser.
+exposes this convenient method which logs and returns a URL that can be opened
+in a browser.
 
 ```javascript
 import {screen} from '@testing-library/dom'

docs/dom-testing-library/setup.mdx

@@ -18,9 +18,10 @@ the DOM and browser APIs that runs in node. If you're not using Jest and you
 would like to run your tests in Node, then you must install jsdom yourself.
 There's also a package called
 [global-jsdom](https://github.com/modosc/global-jsdom) which can be used to
-setup the global environment to simulate the browser APIs. Note that if you're using
-Vitest you only need to configure [`environment`](https://vitest.dev/config/#environment)
-to `jsdom` to achieve the same effect, you don't need global-jsdom.
+setup the global environment to simulate the browser APIs. Note that if you're
+using Vitest you only need to configure
+[`environment`](https://vitest.dev/config/#environment) to `jsdom` to achieve
+the same effect, you don't need global-jsdom.
 
 First, install jsdom and global-jsdom.
 

docs/ecosystem-user-event.mdx

@@ -615,22 +615,27 @@ method.
 Usage example:
 
 ```jsx
-import React, { useState } from 'react'
+import React, {useState} from 'react'
 import {render, screen} from '@testing-library/react'
 import userEvent, {specialChars} from '@testing-library/user-event'
 
 const InputElement = () => {
-  const [currentValue, setCurrentValue] = useState('This is a bad example');
-  return <div>
-    <label htmlFor='my-input'>Example:</label>
-    <input id='my-input' type='text' value={currentValue} onChange={(e) => setCurrentValue(e.target.value)} />
-  </div>;
+  const [currentValue, setCurrentValue] = useState('This is a bad example')
+  return (
+    <div>
+      <label htmlFor="my-input">Example:</label>
+      <input
+        id="my-input"
+        type="text"
+        value={currentValue}
+        onChange={e => setCurrentValue(e.target.value)}
+      />
+    </div>
+  )
 }
 
 test('delete characters within the selectedRange', () => {
-  render(
-    <InputElement/>,
-  )
+  render(<InputElement />)
   const input = screen.getByLabelText(/example/i)
   input.setSelectionRange(10, 13)
   userEvent.type(input, `${specialChars.backspace}good`)

docs/example-external.mdx

@@ -6,7 +6,8 @@ sidebar_label: External Examples
 
 ## Code Samples
 
-- You can find more React Testing Library examples at [https://react-testing-examples.netlify.app/](https://react-testing-examples.netlify.app/).
+- You can find more React Testing Library examples at
+  [https://react-testing-examples.netlify.app/](https://react-testing-examples.netlify.app/).
 
 ## Playground
 

docs/example-formik.md

@@ -65,9 +65,12 @@ test('rendering and submitting a basic Formik form', async () => {
   render(<MyForm onSubmit={handleSubmit} />)
   const user = userEvent.setup()
 
-  await user.type(screen.getByRole("textbox", { name: /first name/i }), 'John')
-  await user.type(screen.getByRole("textbox", { name: /last name/i }), 'Dee')
-  await user.type(screen.getByRole("textbox", { name: /email/i }), 'john.dee@someemail.com')
+  await user.type(screen.getByRole('textbox', {name: /first name/i}), 'John')
+  await user.type(screen.getByRole('textbox', {name: /last name/i}), 'Dee')
+  await user.type(
+    screen.getByRole('textbox', {name: /email/i}),
+    'john.dee@someemail.com',
+  )
 
   await user.click(screen.getByRole('button', {name: /submit/i}))
 

docs/example-react-router.mdx

@@ -168,7 +168,8 @@ export const App = () => (
 ```
 
 In your tests, pass the history object as a whole to the Router component.
-**Note:** React Router v5 [only works with History v4](https://github.com/remix-run/history#documentation),
+**Note:** React Router v5
+[only works with History v4](https://github.com/remix-run/history#documentation),
 so make sure you have the correct version of `history` installed.
 
 ```jsx

docs/learning.mdx

@@ -43,10 +43,14 @@ sidebar_label: Learning Material
   [Daniel Afonso](https://twitter.com/danieljcafonso)
 - [Testing Apollo Components Using react-testing-library](https://www.arahansen.com/testing-apollo-components-using-react-testing-library/)
   by [Andrew Hansen](https://twitter.com/arahansen)
-- [Enzyme vs React Testing Library: A Migration Guide](https://claritydev.net/blog/enzyme-vs-react-testing-library-migration-guide) by [Alex Khomenko](https://claritydev.net)
-- [Testing React Hook Form With React Testing Library](https://claritydev.net/blog/testing-react-hook-form-with-react-testing-library) by [Alex Khomenko](https://claritydev.net)
-- [Improving React Testing Library Tests](https://claritydev.net/blog/improving-react-testing-library-tests) by [Alex Khomenko](https://claritydev.net)   
-- [Testing Angular Challenges](https://angular-challenges.vercel.app/challenges/testing/) by [Thomas Laforge](https://twitter.com/laforge_toma)
+- [Enzyme vs React Testing Library: A Migration Guide](https://claritydev.net/blog/enzyme-vs-react-testing-library-migration-guide)
+  by [Alex Khomenko](https://claritydev.net)
+- [Testing React Hook Form With React Testing Library](https://claritydev.net/blog/testing-react-hook-form-with-react-testing-library)
+  by [Alex Khomenko](https://claritydev.net)
+- [Improving React Testing Library Tests](https://claritydev.net/blog/improving-react-testing-library-tests)
+  by [Alex Khomenko](https://claritydev.net)
+- [Testing Angular Challenges](https://angular-challenges.vercel.app/challenges/testing/)
+  by [Thomas Laforge](https://twitter.com/laforge_toma)
 
 ## Portuguese 🇧🇷
 
@@ -61,6 +65,7 @@ sidebar_label: Learning Material
 
 - [TESTING en REACT 🧪 ¡Aprende DESDE CERO! Con react-testing-library y Jest](https://www.youtube.com/watch?v=KYjjtRgg_H0)
   by [Midudev](https://twitter.com/midudev)
-- [Buenas prácticas con Angular Testing Library](https://dev.to/danyparedes/buenas-practicas-con-angular-testing-library-59lp) by [Danywalls](https://twitter.com/danywalls)
+- [Buenas prácticas con Angular Testing Library](https://dev.to/danyparedes/buenas-practicas-con-angular-testing-library-59lp)
+  by [Danywalls](https://twitter.com/danywalls)
 
 Feel free to contribute more!