You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7ec733a
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/src/use/core-concepts/glossary.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ ESLint [rules](#rule) are given an AST and may produce [violations](#violation)
27
27
28
28
A file containing preferences for how ESLint should parse files and run [rules](#rule).
29
29
30
-
ESLint config files are named like `eslint.config.(c|m)js`.
30
+
ESLint config files are named like `eslint.config.(c|m)?(j|t)s`.
31
31
Each config file exports a [config array](#config-array) containing [config objects](#config-object).
32
32
33
33
For example, this `eslint.config.js` file enables the `prefer-const`[rule](#rule) at the _error_[severity](#severity):
@@ -124,7 +124,7 @@ Rule violations may also include file changes that are unsafe and not automatica
124
124
125
125
The current configuration file format for ESLint.
126
126
127
-
Flat config files are named in the format `eslint.config.(c|m)?js`.
127
+
Flat config files are named in the format `eslint.config.(c|m)?(j|t)s`.
128
128
"Flat" config files are named as such because all nesting must be done in one configuration file.
129
129
In contrast, the ["Legacy" config format](#legacy-config) allowed nesting configuration files in sub-directories within a project.
130
130
@@ -220,9 +220,9 @@ Note that a _linter_ is separate from [formatters](#formatter-tool) and [type ch
220
220
221
221
A [rule](#rule) that inspects how code operates to find problems.
222
222
223
-
Many logical rules look for likely crashes (e.g. [`no-undef`](../../rules/no-undef)), unintended behavior (e.g. [`no-sparse-arrays`](../../rules/no-sparse-arrays)), and unused code (e.g [`no-unused-vars`](../../rules/no-unused-vars)).
223
+
Many logical rules look for likely crashes (e.g. [`no-undef`](../../rules/no-undef)), unintended behavior (e.g. [`no-sparse-arrays`](../../rules/no-sparse-arrays)), and unused code (e.g.[`no-unused-vars`](../../rules/no-unused-vars)).
224
224
225
-
You can see the full list of logical rules that ship with ESLint under [Rules > Possible Problems](../../rules/#possible-problems)
225
+
You can see the full list of logical rules that ship with ESLint under [Rules > Possible Problems](../../rules/#possible-problems).
226
226
227
227
## N
228
228
@@ -233,7 +233,7 @@ A section of code within an [AST](#abstract-syntax-tree-ast).
233
233
Each node represents a type of syntax found in source code.
234
234
For example, the `1 + 2` in the AST for `1 + 2;` is a _BinaryExpression_.
235
235
236
-
See [#esquery](#esquery) for the library ESLint uses to parse [selectors](#selector) that allow [rules](#rule) to search for nodes.
236
+
See [ESQuery](#esquery) for the library ESLint uses to parse [selectors](#selector) that allow [rules](#rule) to search for nodes.
237
237
238
238
## O
239
239
@@ -297,7 +297,7 @@ A part of a plugin that extracts JavaScript code from other kinds of files, then
297
297
298
298
For example, [`@eslint/markdown`](https://github.com/eslint/markdown) includes a processor that converts the text of <code>```</code> code blocks in Markdown files into code that can be linted.
299
299
300
-
For more information on configuring processor, see [Plugins > Specify a Processor](../configure/plugins#specify-a-processor).
300
+
For more information on configuring processors, see [Plugins > Specify a Processor](../configure/plugins#specify-a-processor).
301
301
302
302
## R
303
303
@@ -339,7 +339,7 @@ For documentation on configuring rules, see [Configure Rules](../configure/rules
339
339
340
340
### Shareable Config (Configuration)
341
341
342
-
A module that provides a predefined [config file](#config-file-configuration-file) configurations.
342
+
A module that provides predefined [config file](#config-file-configuration-file) configurations.
343
343
344
344
Shareable configs can configure all the same information from config files, including [plugins](#plugin) and [rules](#rule).
345
345
@@ -380,7 +380,7 @@ For more information, see [Changes to our rules policies](https://eslint.org/blo
380
380
An optional augmentation to a [rule](#rule)[violation](#violation) that describes how one may manually adjust the code to address the violation.
381
381
382
382
Suggestions are not generally safe to apply automatically because they cause code behavior changes.
383
-
ESLint does not apply suggestions directly but does provide suggestion to integrations that may choose to apply suggestions (such as an editor extension).
383
+
ESLint does not apply suggestions directly but does provide suggestions to integrations that may choose to apply suggestions (such as an editor extension).
384
384
385
385
Rule violations may also include file changes that are safe and may be automatically applied in the form of [fixes](#fix).
386
386
@@ -394,13 +394,13 @@ Type checkers are generally slower and more comprehensive than linters.
394
394
Whereas linters traditionally operate only on a single file's or snippet's [AST](#abstract-syntax-tree-ast) at a time, type checkers understand cross-file dependencies and types.
395
395
396
396
[TypeScript](https://typescriptlang.org) is the most common type checker for JavaScript.
397
-
The [typescript-eslint](https://typescript-eslint.io) project provides integrations that allow using type checker in lint rules.
397
+
The [typescript-eslint](https://typescript-eslint.io) project provides integrations that allow using type checkers in lint rules.
398
398
399
399
## V
400
400
401
401
### Violation
402
402
403
403
An indication from a [rule](#rule) that an area of code doesn't meet the expectation of the rule.
404
404
405
-
Rule violations indicate a range in source code and error message explaining the violation.
405
+
Rule violations indicate a range in source code and an error message explaining the violation.
406
406
Violations may also optionally include a [fix](#fix) and/or [suggestions](#suggestion) that indicate how to improve the violating code.
0 commit comments