Skip to content

Commit ec7b68a

Browse files
docs: transform bold texts into headings
Co-authored-by: Michaël De Boey <info@michaeldeboey.be>
1 parent 94fd92e commit ec7b68a

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

README.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,8 @@ Then configure the rules you want to use within `rules` property of your `.eslin
7474

7575
With the default setup mentioned before, `eslint-plugin-testing-library` will be run against your whole codebase. If you want to run this plugin only against your tests files, you have the following options:
7676

77-
**ESLint `overrides`**
77+
#### ESLint `overrides`
78+
7879
One way of restricting ESLint config by file patterns is by using [ESLint `overrides`](https://eslint.org/docs/user-guide/configuring/configuration-files#configuration-based-on-glob-patterns).
7980

8081
Assuming you are using the same pattern for your test files as [Jest by default](https://jestjs.io/docs/configuration#testmatch-arraystring), the following config would run `eslint-plugin-testing-library` only against your test files:
@@ -98,7 +99,8 @@ Assuming you are using the same pattern for your test files as [Jest by default]
9899
};
99100
```
100101

101-
**ESLint Cascading and Hierachy**
102+
#### ESLint Cascading and Hierachy
103+
102104
Another approach for customizing ESLint config by paths is through [ESLint Cascading and Hierachy](https://eslint.org/docs/user-guide/configuring/configuration-files#cascading-and-hierarchy). This is useful if all your tests are placed under the same folder, so you can place there another `.eslintrc` where you enable `eslint-plugin-testing-library` for applying it only to the files under such folder, rather than enabling it on your global `.eslintrc` which would apply to your whole project.
103105

104106
## Shareable configurations

0 commit comments

Comments
 (0)