diff --git a/.typos.toml b/.typos.toml index 84ce2e0d4f..9d50f863cb 100644 --- a/.typos.toml +++ b/.typos.toml @@ -5,6 +5,7 @@ [default.extend-words] trivias = "trivias" trivia = "trivia" +inferrable = "inferrable" [files] extend-exclude = ["src/docs/guide/usage/linter/rules", "pnpm-lock.yaml"] diff --git a/src/docs/guide/usage/linter/generated-config.md b/src/docs/guide/usage/linter/generated-config.md index ed5cc58129..1be7d7560a 100644 --- a/src/docs/guide/usage/linter/generated-config.md +++ b/src/docs/guide/usage/linter/generated-config.md @@ -108,6 +108,14 @@ Globals can be disabled by setting their value to `"off"`. For example, in an en You may also use `"readable"` or `false` to represent `"readonly"`, and `"writeable"` or `true` to represent `"writable"`. +## ignorePatterns + +type: `string[]` + +default: `[]` + +Globs to ignore during linting. These are resolved from the configuration file path. + ## overrides type: `array` @@ -144,8 +152,6 @@ type: `object` Configure the behavior of linter plugins. -## Example - Here's an example if you're using Next.js in a monorepo: ```json @@ -254,7 +260,7 @@ default: `{}` To have your custom components be checked as DOM elements, you can provide a mapping of your component names to the DOM element name. -## Example +Example: `json { "settings": { "jsx-a11y": { "components": { "Link": "a", "IconButton": "button" } } } } ` @@ -297,7 +303,7 @@ default: `[]` Components used as alternatives to `