@typescript-eslint/eslint-plugin 7.2.1-alpha.1 → 7.2.1-alpha.3

package/docs/rules/{no-this-alias.md → no-this-alias.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow aliasing `this`.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-this-alias** for documentation.
@@ -11,9 +14,8 @@ or not managing scope well.
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 const self = this;
@@ -23,7 +25,8 @@ setTimeout(function () {
 });
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 setTimeout(() => {
@@ -31,6 +34,9 @@ setTimeout(() => {
 });
 ```
 
+</TabItem>
+</Tabs>
+
 ## Options
 
 ### `allowDestructuring`
@@ -41,9 +47,8 @@ You can explicitly disallow them by setting `allowDestructuring` to `false`.
 
 Examples of code for the `{ "allowDestructuring": false }` option:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowDestructuring": false }'
 class ComponentLike {
@@ -59,7 +64,8 @@ class ComponentLike {
 }
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowDestructuring": false }'
 class ComponentLike {
@@ -73,6 +79,9 @@ class ComponentLike {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowedNames`
 
 `no-this-alias` can alternately be used to allow only a specific list of names as `this` aliases.
@@ -80,9 +89,8 @@ We recommend against this except as a transitory step towards fixing all rule vi
 
 Examples of code for the `{ "allowedNames": ["self"] }` option:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowedNames": ["self"] }'
 class Example {
@@ -92,7 +100,8 @@ class Example {
 }
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowedNames": ["self"] }'
 class Example {
@@ -102,6 +111,9 @@ class Example {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If your project is structured in a way that it needs to assign `this` to variables, this rule is likely not for you.

package/docs/rules/{no-throw-literal.md → no-throw-literal.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow throwing literals as exceptions.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-throw-literal** for documentation.
@@ -15,9 +18,8 @@ This rule restricts what can be thrown as an exception. When it was first create
 
 This rule is aimed at maintaining consistency when throwing exception by disallowing to throw literals and other expressions which cannot possibly be an `Error` object.
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 throw 'error';
@@ -48,7 +50,8 @@ const foo = {
 throw foo.bar;
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 throw new Error();
@@ -83,6 +86,9 @@ class CustomError extends Error {
 throw new CustomError();
 ```
 
+</TabItem>
+</Tabs>
+
 ## Options
 
 This rule adds the following options:
@@ -106,4 +112,4 @@ const defaultOptions: Options = {
 };
 ```
 
-<!-- Intentionally omitted: When Not To Use It -->
+{/* Intentionally Omitted: When Not To Use It */}

package/docs/rules/{no-type-alias.md → no-type-alias.mdx}

@@ -2,13 +2,16 @@
 description: 'Disallow type aliases.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-type-alias** for documentation.
 
 :::danger Deprecated
 
-This rule has been deprecated in favour of the [`@typescript-eslint/consistent-type-definitions`](./consistent-type-definitions.md) rule.
+This rule has been deprecated in favour of the [`@typescript-eslint/consistent-type-definitions`](./consistent-type-definitions.mdx) rule.
 TypeScript type aliases are a commonly necessary language feature; banning it altogether is oftentimes counterproductive.
 
 :::
@@ -616,7 +619,7 @@ type Foo = Partial<Bar>;
 type Foo = Omit<Bar, 'a' | 'b'>;
 ```
 
-<!-- Intentionally Omitted: When Not To Use It -->
+{/* Intentionally Omitted: When Not To Use It */}
 
 ## Further Reading
 

package/docs/rules/{no-unnecessary-boolean-literal-compare.md → no-unnecessary-boolean-literal-compare.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow unnecessary equality comparisons against boolean literals.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unnecessary-boolean-literal-compare** for documentation.
@@ -21,9 +24,8 @@ However, the implementation of the rule does not distinguish between strict and
 Any example below that uses `===` would be treated the same way if `==` was used, and `!==` would be treated the same way if `!=` was used.
 :::
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 declare const someCondition: boolean;
@@ -31,7 +33,8 @@ if (someCondition === true) {
 }
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 declare const someCondition: boolean;
@@ -47,6 +50,9 @@ if (someStringBoolean === true) {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ## Options
 
 This rule always checks comparisons between a boolean variable and a boolean
@@ -57,9 +63,8 @@ are **not** checked by default.
 
 Examples of code for this rule with `{ allowComparingNullableBooleansToTrue: false }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowComparingNullableBooleansToTrue": false }'
 declare const someUndefinedCondition: boolean | undefined;
@@ -71,7 +76,8 @@ if (someNullCondition !== true) {
 }
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowComparingNullableBooleansToTrue": false }'
 declare const someUndefinedCondition: boolean | undefined;
@@ -83,13 +89,15 @@ if (!someNullCondition) {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowComparingNullableBooleansToFalse`
 
 Examples of code for this rule with `{ allowComparingNullableBooleansToFalse: false }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowComparingNullableBooleansToFalse": false }'
 declare const someUndefinedCondition: boolean | undefined;
@@ -101,7 +109,8 @@ if (someNullCondition !== false) {
 }
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowComparingNullableBooleansToFalse": false }'
 declare const someUndefinedCondition: boolean | undefined;
@@ -113,6 +122,9 @@ if (!(someNullCondition ?? true)) {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ## Fixer
 
 |            Comparison             | Fixer Output                    | Notes                                                                               |

package/docs/rules/{no-unnecessary-condition.md → no-unnecessary-condition.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow conditionals where the type is always truthy or always falsy.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unnecessary-condition** for documentation.
@@ -17,9 +20,8 @@ The following expressions are checked:
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 function head<T>(items: T[]) {
@@ -47,7 +49,8 @@ function bar<T>(arg: string) {
 ].filter(t => t); // number[] is always truthy
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 function head<T>(items: T[]) {
@@ -71,6 +74,9 @@ function bar(arg?: string | null) {
 [0, 1, 2, 3].filter(t => t); // number can be truthy or falsy
 ```
 
+</TabItem>
+</Tabs>
+
 ## Options
 
 ### `allowConstantLoopConditions`
@@ -116,4 +122,4 @@ if (condition) {
 ## Related To
 
 - ESLint: [no-constant-condition](https://eslint.org/docs/rules/no-constant-condition) - `no-unnecessary-condition` is essentially a stronger version of `no-constant-condition`, but requires type information.
-- [strict-boolean-expressions](./strict-boolean-expressions.md) - a more opinionated version of `no-unnecessary-condition`. `strict-boolean-expressions` enforces a specific code style, while `no-unnecessary-condition` is about correctness.
+- [strict-boolean-expressions](./strict-boolean-expressions.mdx) - a more opinionated version of `no-unnecessary-condition`. `strict-boolean-expressions` enforces a specific code style, while `no-unnecessary-condition` is about correctness.

package/docs/rules/{no-unnecessary-qualifier.md → no-unnecessary-qualifier.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow unnecessary namespace qualifiers.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unnecessary-qualifier** for documentation.
@@ -12,9 +15,8 @@ This rule reports when an enum or namespace qualifier is unnecessary.
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 enum A {
@@ -30,7 +32,8 @@ namespace A {
 }
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 enum A {
@@ -46,6 +49,9 @@ namespace A {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If you explicitly prefer to use fully qualified names, such as for explicitness, then you don't need to use this rule.

package/docs/rules/{no-unnecessary-type-arguments.md → no-unnecessary-type-arguments.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow type arguments that are equal to the default.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unnecessary-type-arguments** for documentation.
@@ -20,9 +23,8 @@ This rule reports when an explicitly specified type argument is the default for
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 function f<T = number>() {}
@@ -46,7 +48,8 @@ interface I<T = number> {}
 class Impl implements I<number> {}
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 function f<T = number>() {}
@@ -74,6 +77,9 @@ interface I<T = number> {}
 class Impl implements I<string> {}
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If you prefer explicitly specifying type parameters even when they are equal to the default, you can skip this rule.

package/docs/rules/{no-unnecessary-type-assertion.md → no-unnecessary-type-assertion.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow type assertions that do not change the type of an expression.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unnecessary-type-assertion** for documentation.
@@ -12,9 +15,8 @@ This rule reports when a type assertion does not change the type of an expressio
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 const foo = 3;
@@ -41,7 +43,8 @@ function foo(x: number): number {
 }
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 const foo = <number>3;
@@ -61,6 +64,9 @@ function foo(x: number | undefined): number {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ## Options
 
 ### `typesToIgnore`

package/docs/rules/{no-unnecessary-type-constraint.md → no-unnecessary-type-constraint.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow unnecessary constraints on generic types.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unnecessary-type-constraint** for documentation.
@@ -12,9 +15,8 @@ It is therefore redundant to `extend` from `any` or `unknown`.
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 interface FooAny<T extends any> {}
@@ -34,7 +36,8 @@ const QuuxAny = <T extends any>() => {};
 function QuuzAny<T extends any>() {}
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 interface Foo<T> {}
@@ -50,6 +53,9 @@ const Quux = <T>() => {};
 function Quuz<T>() {}
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If you don't care about the specific styles of your type constraints, or never use them in the first place, then you will not need this rule.

package/docs/rules/{no-unsafe-argument.md → no-unsafe-argument.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow calling a function with a value with type `any`.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unsafe-argument** for documentation.
@@ -20,9 +23,8 @@ For example, it will error if you pass `Set<any>` as an argument to a parameter
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 declare function foo(arg1: string, arg2: number, arg3: string): void;
@@ -49,7 +51,8 @@ declare function baz(arg1: Set<string>, arg2: Map<string, string>): void;
 foo(new Set<any>(), new Map<any, string>());
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 declare function foo(arg1: string, arg2: number, arg3: string): void;
@@ -67,7 +70,8 @@ declare function baz(arg1: Set<string>, arg2: Map<string, string>): void;
 foo(new Set<string>(), new Map<string, string>());
 ```
 
-<!--/tabs-->
+</TabItem>
+</Tabs>
 
 There are cases where the rule allows passing an argument of `any` to `unknown`.
 
@@ -86,8 +90,8 @@ You might consider using [ESLint disable comments](https://eslint.org/docs/lates
 
 ## Related To
 
-- [`no-explicit-any`](./no-explicit-any.md)
-- [`no-unsafe-assignment`](./no-unsafe-assignment.md)
-- [`no-unsafe-call`](./no-unsafe-call.md)
-- [`no-unsafe-member-access`](./no-unsafe-member-access.md)
-- [`no-unsafe-return`](./no-unsafe-return.md)
+- [`no-explicit-any`](./no-explicit-any.mdx)
+- [`no-unsafe-assignment`](./no-unsafe-assignment.mdx)
+- [`no-unsafe-call`](./no-unsafe-call.mdx)
+- [`no-unsafe-member-access`](./no-unsafe-member-access.mdx)
+- [`no-unsafe-return`](./no-unsafe-return.mdx)

package/docs/rules/{no-unsafe-assignment.md → no-unsafe-assignment.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow assigning a value with type `any` to variables and properties.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unsafe-assignment** for documentation.
@@ -19,9 +22,8 @@ For example, it will error if you assign `Set<any>` to a variable declared as `S
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 const x = 1 as any,
@@ -46,7 +48,8 @@ const x: Set<string[]> = new Set<any[]>();
 const x: Set<Set<Set<string>>> = new Set<Set<Set<any>>>();
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 const x = 1,
@@ -69,7 +72,8 @@ const x: Set<string[]> = new Set<string[]>();
 const x: Set<Set<Set<string>>> = new Set<Set<Set<string>>>();
 ```
 
-<!--/tabs-->
+</TabItem>
+</Tabs>
 
 There are cases where the rule allows assignment of `any` to `unknown`.
 
@@ -89,8 +93,8 @@ You might consider using [ESLint disable comments](https://eslint.org/docs/lates
 
 ## Related To
 
-- [`no-explicit-any`](./no-explicit-any.md)
-- [`no-unsafe-argument`](./no-unsafe-argument.md)
-- [`no-unsafe-call`](./no-unsafe-call.md)
-- [`no-unsafe-member-access`](./no-unsafe-member-access.md)
-- [`no-unsafe-return`](./no-unsafe-return.md)
+- [`no-explicit-any`](./no-explicit-any.mdx)
+- [`no-unsafe-argument`](./no-unsafe-argument.mdx)
+- [`no-unsafe-call`](./no-unsafe-call.mdx)
+- [`no-unsafe-member-access`](./no-unsafe-member-access.mdx)
+- [`no-unsafe-return`](./no-unsafe-return.mdx)

package/docs/rules/{no-unsafe-call.md → no-unsafe-call.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow calling a value with type `any`.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unsafe-call** for documentation.
@@ -16,9 +19,8 @@ This rule disallows calling any value that is typed as `any`.
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 declare const anyVar: any;
@@ -37,7 +39,8 @@ anyVar`foo`;
 nestedAny.prop`foo`;
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 declare const typedVar: () => void;
@@ -53,6 +56,9 @@ new Map();
 String.raw`foo`;
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If your codebase has many existing `any`s or areas of unsafe code, it may be difficult to enable this rule.
@@ -61,8 +67,8 @@ You might consider using [ESLint disable comments](https://eslint.org/docs/lates
 
 ## Related To
 
-- [`no-explicit-any`](./no-explicit-any.md)
-- [`no-unsafe-argument`](./no-unsafe-argument.md)
-- [`no-unsafe-assignment`](./no-unsafe-assignment.md)
-- [`no-unsafe-member-access`](./no-unsafe-member-access.md)
-- [`no-unsafe-return`](./no-unsafe-return.md)
+- [`no-explicit-any`](./no-explicit-any.mdx)
+- [`no-unsafe-argument`](./no-unsafe-argument.mdx)
+- [`no-unsafe-assignment`](./no-unsafe-assignment.mdx)
+- [`no-unsafe-member-access`](./no-unsafe-member-access.mdx)
+- [`no-unsafe-return`](./no-unsafe-return.mdx)

package/docs/rules/{no-unsafe-declaration-merging.md → no-unsafe-declaration-merging.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow unsafe declaration merging.'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 > 🛑 This file is source code, not the primary documentation location! 🛑
 >
 > See **https://typescript-eslint.io/rules/no-unsafe-declaration-merging** for documentation.
@@ -25,9 +28,8 @@ foo.nums.push(1); // Runtime Error: Cannot read properties of undefined.
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 interface Foo {}
@@ -35,7 +37,8 @@ interface Foo {}
 class Foo {}
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 interface Foo {}
@@ -49,6 +52,9 @@ namespace Qux {}
 function Qux() {}
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If your project intentionally defines classes and interfaces with unsafe declaration merging patterns, this rule might not be for you.