Release 1.26.0 (#604)

Author: Boshen

src/docs/guide/usage/linter/generated-config.md

@@ -95,7 +95,8 @@ type: `Record<string, boolean>`
 
 Predefine global variables.
 
-Environments specify what global variables are predefined. See [ESLint's list of environments](https://eslint.org/docs/v8.x/use/configure/language-options#specifying-environments)
+Environments specify what global variables are predefined.
+See [ESLint's list of environments](https://eslint.org/docs/v8.x/use/configure/language-options#specifying-environments)
 for what environments are available and what each one provides.
 
 ## extends

src/docs/guide/usage/linter/generated-rules.md

@@ -2,7 +2,7 @@
 
 The progress of all rule implementations is tracked [here](https://github.com/oxc-project/oxc/issues/481).
 
-- Total number of rules: 611
+- Total number of rules: 613
 - Rules turned on by default: 103
 
 **Legend for 'Fixable?' column:**
@@ -13,7 +13,7 @@ The progress of all rule implementations is tracked [here](https://github.com/ox
 - ⚠️💡: a dangerous suggestion is available for this rule
 - 🚧: an auto-fix or suggestion is possible, but currently not implemented
 
-## Correctness (197):
+## Correctness (196):
 
 Code that is outright wrong or useless.
 
@@ -161,7 +161,6 @@ Code that is outright wrong or useless.
 | [forward-ref-uses-ref](/docs/guide/usage/linter/rules/react/forward-ref-uses-ref.html)                                                                | react      |         | 💡       |
 | [jsx-key](/docs/guide/usage/linter/rules/react/jsx-key.html)                                                                                          | react      |         |          |
 | [jsx-no-duplicate-props](/docs/guide/usage/linter/rules/react/jsx-no-duplicate-props.html)                                                            | react      |         |          |
-| [jsx-no-target-blank](/docs/guide/usage/linter/rules/react/jsx-no-target-blank.html)                                                                  | react      |         |          |
 | [jsx-no-undef](/docs/guide/usage/linter/rules/react/jsx-no-undef.html)                                                                                | react      |         |          |
 | [jsx-props-no-spread-multi](/docs/guide/usage/linter/rules/react/jsx-props-no-spread-multi.html)                                                      | react      |         | 🛠️        |
 | [no-children-prop](/docs/guide/usage/linter/rules/react/no-children-prop.html)                                                                        | react      |         |          |
@@ -374,7 +373,7 @@ code that is most likely wrong or useless.
 | [no-required-prop-with-default](/docs/guide/usage/linter/rules/vue/no-required-prop-with-default.html)                          | vue        |         | 🚧       |
 | [require-default-export](/docs/guide/usage/linter/rules/vue/require-default-export.html)                                        | vue        |         |          |
 
-## Pedantic (103):
+## Pedantic (105):
 
 Lints which are rather strict or have occasional false positives.
 
@@ -416,12 +415,14 @@ Lints which are rather strict or have occasional false positives.
 | [require-returns-description](/docs/guide/usage/linter/rules/jsdoc/require-returns-description.html)                           | jsdoc      |         |          |
 | [require-returns-type](/docs/guide/usage/linter/rules/jsdoc/require-returns-type.html)                                         | jsdoc      |         |          |
 | [checked-requires-onchange-or-readonly](/docs/guide/usage/linter/rules/react/checked-requires-onchange-or-readonly.html)       | react      |         |          |
+| [jsx-no-target-blank](/docs/guide/usage/linter/rules/react/jsx-no-target-blank.html)                                           | react      |         |          |
 | [jsx-no-useless-fragment](/docs/guide/usage/linter/rules/react/jsx-no-useless-fragment.html)                                   | react      |         | 💡       |
 | [no-unescaped-entities](/docs/guide/usage/linter/rules/react/no-unescaped-entities.html)                                       | react      |         |          |
 | [rules-of-hooks](/docs/guide/usage/linter/rules/react/rules-of-hooks.html)                                                     | react      |         |          |
 | [ban-ts-comment](/docs/guide/usage/linter/rules/typescript/ban-ts-comment.html)                                                | typescript |         | 🛠️        |
 | [ban-types](/docs/guide/usage/linter/rules/typescript/ban-types.html)                                                          | typescript |         | 🚧       |
 | [no-confusing-void-expression](/docs/guide/usage/linter/rules/typescript/no-confusing-void-expression.html)                    | typescript |         | 🚧       |
+| [no-deprecated](/docs/guide/usage/linter/rules/typescript/no-deprecated.html)                                                  | typescript |         |          |
 | [no-misused-promises](/docs/guide/usage/linter/rules/typescript/no-misused-promises.html)                                      | typescript |         | 🚧       |
 | [no-mixed-enums](/docs/guide/usage/linter/rules/typescript/no-mixed-enums.html)                                                | typescript |         | 🚧       |
 | [no-unsafe-argument](/docs/guide/usage/linter/rules/typescript/no-unsafe-argument.html)                                        | typescript |         | 🚧       |
@@ -484,7 +485,7 @@ Lints which are rather strict or have occasional false positives.
 | [prefer-type-error](/docs/guide/usage/linter/rules/unicorn/prefer-type-error.html)                                             | unicorn    |         | 🛠️        |
 | [require-number-to-fixed-digits-argument](/docs/guide/usage/linter/rules/unicorn/require-number-to-fixed-digits-argument.html) | unicorn    |         | 🛠️        |
 
-## Style (164):
+## Style (165):
 
 Code that should be written in a more idiomatic way.
 
@@ -597,6 +598,7 @@ Code that should be written in a more idiomatic way.
 | [no-set-state](/docs/guide/usage/linter/rules/react/no-set-state.html)                                                   | react      |         |          |
 | [prefer-es6-class](/docs/guide/usage/linter/rules/react/prefer-es6-class.html)                                           | react      |         |          |
 | [self-closing-comp](/docs/guide/usage/linter/rules/react/self-closing-comp.html)                                         | react      |         | 🛠️        |
+| [state-in-constructor](/docs/guide/usage/linter/rules/react/state-in-constructor.html)                                   | react      |         |          |
 | [adjacent-overload-signatures](/docs/guide/usage/linter/rules/typescript/adjacent-overload-signatures.html)              | typescript |         |          |
 | [array-type](/docs/guide/usage/linter/rules/typescript/array-type.html)                                                  | typescript |         | 🛠️        |
 | [ban-tslint-comment](/docs/guide/usage/linter/rules/typescript/ban-tslint-comment.html)                                  | typescript |         | 🛠️        |

src/docs/guide/usage/linter/rules/eslint/class-methods-use-this.md

@@ -48,6 +48,54 @@ class C {
 }
 ```
 
+## Configuration
+
+This rule accepts a configuration object with the following properties:
+
+### enforceForClassFields
+
+type: `boolean`
+
+default: `true`
+
+Enforce this rule for class fields that are functions.
+
+### exceptMethods
+
+type: `array`
+
+default: `[]`
+
+List of method names to exempt from this rule.
+
+#### exceptMethods[n]
+
+type: `object`
+
+##### exceptMethods[n].name
+
+type: `string`
+
+##### exceptMethods[n].private
+
+type: `boolean`
+
+### ignoreClassesWithImplements
+
+type: `"all" | "public-fields"`
+
+default: `null`
+
+Whether to ignore classes that implement interfaces.
+
+### ignoreOverrideMethods
+
+type: `boolean`
+
+default: `false`
+
+Whether to ignore methods that are overridden.
+
 ## How to use
 
 To **enable** this rule in the CLI or using the config file, you can use:

src/docs/guide/usage/linter/rules/eslint/curly.md

@@ -25,35 +25,6 @@ Omitting curly braces can reduce code readability and increase the likelihood of
 It can also lead to bugs if additional statements are added later without properly enclosing them in braces.
 Using curly braces consistently makes the code safer and easier to modify.
 
-### Options
-
-First option:
-
-- Type: `string`
-- Default: `"all"`
-- Possible values:
-  - `"all"`: require braces in all cases
-  - `"multi"`: require braces only for multi-statement blocks
-  - `"multi-line"`: require braces only for multi-line blocks
-  - `"multi-or-nest"`: require braces for multi-line blocks or when nested
-
-Second option:
-
-- Type: `string`
-- Default: `undefined`
-- Possible values:
-- `"consistent"`: require braces if any other branch in the `if-else` chain has braces
-
-Note : The second option can only be used in conjunction with the first option.
-
-Example configuration:
-
-```json
-{
-  "curly": ["error", "multi-or-nest", "consistent"]
-}
-```
-
 ### Examples
 
 #### `"all"` (default)
@@ -254,6 +225,31 @@ if (foo) {
 }
 ```
 
+## Configuration
+
+This rule accepts a configuration object with the following properties:
+
+### consistent
+
+type: `boolean`
+
+default: `false`
+
+Whether to enforce consistent use of curly braces in if-else chains.
+
+### curlyType
+
+type: `"all" | "multi" | "multi-line" | "multi-or-nest"`
+
+default: `"all"`
+
+Which type of curly brace enforcement to use.
+
+- `"all"`: require braces in all cases
+- `"multi"`: require braces only for multi-statement blocks
+- `"multi-line"`: require braces only for multi-line blocks
+- `"multi-or-nest"`: require braces for multi-line blocks or when nested
+
 ## How to use
 
 To **enable** this rule in the CLI or using the config file, you can use:

src/docs/guide/usage/linter/rules/eslint/grouped-accessor-pairs.md

@@ -104,18 +104,15 @@ const foo = {
 };
 ```
 
-### Options
+## Configuration
 
-This rule accepts two arguments:
+This rule accepts a configuration object with the following properties:
 
-1. A string value to control the order of the getter/setter pairs:
-   - `"anyOrder"` (default): Accessors can be in any order
-   - `"getBeforeSet"`: Getters must come before setters
-   - `"setBeforeGet"`: Setters must come before getters
-2. An object with the following option:
-   - `enforceForTSTypes` (boolean, default: false): When enabled, also checks TypeScript interfaces and type aliases for grouped accessor pairs
+### enforceForTSTypes
 
-### TypeScript
+type: `boolean`
+
+default: `false`
 
 When `enforceForTSTypes` is enabled, this rule also applies to TypeScript interfaces and type aliases:
 
@@ -151,6 +148,18 @@ type Bar = {
 };
 ```
 
+### pairOrder
+
+type: `"anyOrder" | "getBeforeSet" | "setBeforeGet"`
+
+default: `"anyOrder"`
+
+A string value to control the order of the getter/setter pairs:
+
+- `"anyOrder"`: Accessors can be in any order
+- `"getBeforeSet"`: Getters must come before setters
+- `"setBeforeGet"`: Setters must come before getters
+
 ## How to use
 
 To **enable** this rule in the CLI or using the config file, you can use:

src/docs/guide/usage/linter/rules/eslint/max-lines-per-function.md

@@ -57,47 +57,43 @@ function foo() {
 }
 ```
 
-### Options
+## Configuration
 
-#### max
+This rule accepts a configuration object with the following properties:
 
-{ type: number, default: 50 }
+### iifes
 
-The `max` enforces a maximum number of lines in a function.
+type: `boolean`
 
-#### skipBlankLines
+default: `false`
 
-{ type: boolean, default: false }
+The `IIFEs` option controls whether IIFEs are included in the line count.
+By default, IIFEs are not considered, but when set to `true`, they will
+be included in the line count for the function.
 
-The `skipBlankLines` ignore lines made up purely of whitespace.
+### max
 
-#### skipComments
+type: `integer`
 
-{ type: boolean, default: false }
+default: `50`
 
-The `skipComments` ignore lines containing just comments.
+Maximum number of lines allowed in a function.
 
-#### IIFEs
+### skipBlankLines
 
-{ type: boolean, default: false }
+type: `boolean`
 
-The `IIFEs` option controls whether IIFEs are included in the line count.
-By default, IIFEs are not considered, but when set to `true`, they will
-be included in the line count for the function.
+default: `false`
 
-Example:
+Skip lines made up purely of whitespace.
 
-```json
-"eslint/max-lines-per-function": [
-  "error",
-  {
-    "max": 50,
-    "skipBlankLines": false,
-    "skipComments": false,
-    "IIFEs": false
-  }
-]
-```
+### skipComments
+
+type: `boolean`
+
+default: `false`
+
+Skip lines containing just comments.
 
 ## How to use
 

src/docs/guide/usage/linter/rules/eslint/max-lines.md

@@ -22,6 +22,34 @@ is not an objective maximum number of lines considered acceptable in a
 file, most people would agree it should not be in the thousands.
 Recommendations usually range from 100 to 500 lines.
 
+## Configuration
+
+This rule accepts a configuration object with the following properties:
+
+### max
+
+type: `integer`
+
+default: `300`
+
+Maximum number of lines allowed per file.
+
+### skipBlankLines
+
+type: `boolean`
+
+default: `false`
+
+Whether to ignore blank lines when counting.
+
+### skipComments
+
+type: `boolean`
+
+default: `false`
+
+Whether to ignore comments when counting.
+
 ## How to use
 
 To **enable** this rule in the CLI or using the config file, you can use:

src/docs/guide/usage/linter/rules/eslint/max-params.md

@@ -53,26 +53,29 @@ let foo = (bar, baz, qux) => {
 };
 ```
 
-### Options
+## Configuration
 
-#### max
+This rule accepts a configuration object with the following properties:
 
-`{ "max": number }`
+### countVoidThis
 
-This option is for changing the maximum allowed number of function parameters.
+type: `boolean`
 
-For example `{ "max": 4 }` would mean that having a function take four
-parameters is allowed which overrides the default of three.
-
-#### countVoidThis
-
-`{ "countVoidThis": boolean }`
+default: `false`
 
 This option is for counting the `this` parameter if it is of type `void`.
 
 For example `{ "countVoidThis": true }` would mean that having a function
 take a `this` parameter of type `void` is counted towards the maximum number of parameters.
 
+### max
+
+type: `integer`
+
+default: `3`
+
+Maximum number of parameters allowed in function definitions.
+
 ## How to use
 
 To **enable** this rule in the CLI or using the config file, you can use: