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

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

@@ -2,6 +2,9 @@
 description: 'Disallow comparing an enum value with a non-enum value.'
 ---
 
+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-enum-comparison** for documentation.
@@ -26,9 +29,8 @@ The above code snippet should instead be written as `vegetable === Vegetable.Asp
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 enum Fruit {
@@ -50,7 +52,8 @@ declare let vegetable: Vegetable;
 vegetable === 'asparagus';
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 enum Fruit {
@@ -72,7 +75,8 @@ declare let vegetable: Vegetable;
 vegetable === Vegetable.Asparagus;
 ```
 
-<!--/tabs-->
+</TabItem>
+</Tabs>
 
 ## When Not To Use It
 

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

@@ -2,6 +2,9 @@
 description: 'Disallow member access on 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-member-access** for documentation.
@@ -16,9 +19,8 @@ This rule disallows member access on any variable that is typed as `any`.
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 declare const anyVar: any;
@@ -41,7 +43,8 @@ arr[anyVar];
 nestedAny[anyVar];
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 declare const properlyTyped: { prop: { a: string } };
@@ -59,6 +62,9 @@ arr[idx];
 arr[idx++];
 ```
 
+</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.
@@ -67,8 +73,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-call`](./no-unsafe-call.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-call`](./no-unsafe-call.mdx)
+- [`no-unsafe-return`](./no-unsafe-return.mdx)

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

@@ -2,6 +2,9 @@
 description: 'Disallow returning a value with type `any` from a function.'
 ---
 
+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-return** for documentation.
@@ -19,9 +22,8 @@ For example, it will error if you return `Set<any>` from a function declared as
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 function foo1() {
@@ -62,7 +64,8 @@ type TAssign = () => Set<string>;
 const assignability2: TAssign = () => new Set<any>([true]);
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 function foo1() {
@@ -82,7 +85,8 @@ type TAssign = () => Set<string>;
 const assignability2: TAssign = () => new Set(['foo']);
 ```
 
-<!--/tabs-->
+</TabItem>
+</Tabs>
 
 There are cases where the rule allows to return `any` to `unknown`.
 
@@ -106,8 +110,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-call`](./no-unsafe-call.md)
-- [`no-unsafe-member-access`](./no-unsafe-member-access.md)
+- [`no-explicit-any`](./no-explicit-any.mdx)
+- [`no-unsafe-argument`](./no-unsafe-argument.mdx)
+- [`no-unsafe-assignment`](./no-unsafe-assignment.mdx)
+- [`no-unsafe-call`](./no-unsafe-call.mdx)
+- [`no-unsafe-member-access`](./no-unsafe-member-access.mdx)

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

@@ -2,6 +2,9 @@
 description: 'Require unary negation to take a number.'
 ---
 
+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-unary-minus** for documentation.
@@ -17,9 +20,8 @@ This rule restricts the unary `-` operator to `number | bigint`.
 
 ## Examples
 
-<!-- tabs -->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 declare const a: string;
@@ -29,7 +31,8 @@ declare const b: {};
 -b;
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 -42;
@@ -51,4 +54,7 @@ declare const e: 1 | 2;
 -e;
 ```
 
-<!-- Intentionally Omitted: When Not To Use It -->
+</TabItem>
+</Tabs>
+
+{/* Intentionally Omitted: When Not To Use It */}

package/docs/rules/{no-unused-expressions.md → no-unused-expressions.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow unused expressions.'
 ---
 
+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-unused-expressions** for documentation.

package/docs/rules/{no-unused-vars.md → no-unused-vars.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow unused variables.'
 ---
 
+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-unused-vars** for documentation.

package/docs/rules/{no-use-before-define.md → no-use-before-define.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow the use of variables before they are defined.'
 ---
 
+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-use-before-define** for documentation.
@@ -35,9 +38,8 @@ If this is `false`, this rule will ignore references to enums, when the referenc
 
 Examples of code for the `{ "enums": true }` option:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "enums": true }'
 const x = Foo.FOO;
@@ -47,7 +49,8 @@ enum Foo {
 }
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "enums": false }'
 function foo() {
@@ -59,6 +62,9 @@ enum Foo {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ### `typedefs`
 
 If this is `true`, this rule warns every reference to a type before the type declaration.

package/docs/rules/{no-useless-constructor.md → no-useless-constructor.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow unnecessary constructors.'
 ---
 
+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-useless-constructor** for documentation.

package/docs/rules/{no-useless-empty-export.md → no-useless-empty-export.mdx}

@@ -2,6 +2,9 @@
 description: "Disallow empty exports that don't change anything in a module file."
 ---
 
+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-useless-empty-export** for documentation.
@@ -18,9 +21,8 @@ This rule reports an `export {}` that doesn't do anything in a file already usin
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 export const value = 'Hello, world!';
@@ -32,7 +34,8 @@ import 'some-other-module';
 export {};
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 export const value = 'Hello, world!';
@@ -42,6 +45,9 @@ export const value = 'Hello, world!';
 import 'some-other-module';
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If you don't mind an empty `export {}` at the bottom of files, you likely don't need this rule.

package/docs/rules/{no-useless-template-literals.md → no-useless-template-literals.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow unnecessary template 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-useless-template-literals** for documentation.
@@ -10,9 +13,8 @@ This rule reports template literals that can be simplified to a normal string li
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 const ab1 = `${'a'}${'b'}`;
@@ -29,7 +31,8 @@ declare const intersectionWithString: string & { _brand: 'test-brand' };
 const wrappedIntersection = `${intersectionWithString}`;
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 const ab1 = 'ab';
@@ -46,7 +49,8 @@ declare const intersectionWithString: string & { _brand: 'test-brand' };
 const wrappedIntersection = intersectionWithString;
 ```
 
-<!--/tabs-->
+</TabItem>
+</Tabs>
 
 ## When Not To Use It
 
@@ -54,4 +58,4 @@ When you want to allow string expressions inside template literals.
 
 ## Related To
 
-- [`restrict-template-expressions`](./restrict-template-expressions.md)
+- [`restrict-template-expressions`](./restrict-template-expressions.mdx)

package/docs/rules/{no-var-requires.md → no-var-requires.mdx}

@@ -2,6 +2,9 @@
 description: 'Disallow `require` statements except in import statements.'
 ---
 
+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-var-requires** for documentation.
@@ -10,9 +13,8 @@ In other words, the use of forms such as `var foo = require("foo")` are banned.
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 var foo = require('foo');
@@ -20,7 +22,8 @@ const foo = require('foo');
 let foo = require('foo');
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 import foo = require('foo');
@@ -28,6 +31,9 @@ require('foo');
 import foo from 'foo';
 ```
 
+</TabItem>
+</Tabs>
+
 ## Options
 
 ### `allow`
@@ -36,20 +42,23 @@ A array of strings. These strings will be compiled into regular expressions with
 
 With `{allow: ['/package\\.json$']}`:
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 const foo = require('../data.json');
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 const foo = require('../package.json');
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If your project frequently uses older CommonJS `require`s, then this rule might not be applicable to you.
@@ -57,4 +66,4 @@ If only a subset of your project uses `require`s then you might consider using [
 
 ## Related To
 
-- [`no-require-imports`](./no-require-imports.md)
+- [`no-require-imports`](./no-require-imports.mdx)

package/docs/rules/{non-nullable-type-assertion-style.md → non-nullable-type-assertion-style.mdx}

@@ -2,6 +2,9 @@
 description: 'Enforce non-null assertions over explicit type casts.'
 ---
 
+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/non-nullable-type-assertion-style** for documentation.
@@ -16,9 +19,8 @@ This rule reports when an `as` cast is doing the same job as a `!` would, and su
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 const maybe = Math.random() > 0.5 ? '' : undefined;
@@ -27,7 +29,8 @@ const definitely = maybe as string;
 const alsoDefinitely = <string>maybe;
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 const maybe = Math.random() > 0.5 ? '' : undefined;
@@ -36,6 +39,9 @@ const definitely = maybe!;
 const alsoDefinitely = maybe!;
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If you don't mind having unnecessarily verbose type assertions, you can avoid this rule.

package/docs/rules/{object-curly-spacing.md → object-curly-spacing.mdx}

@@ -2,6 +2,9 @@
 description: 'Enforce consistent spacing inside braces.'
 ---
 
+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/object-curly-spacing** for documentation.

package/docs/rules/{padding-line-between-statements.md → padding-line-between-statements.mdx}

@@ -2,6 +2,9 @@
 description: 'Require or disallow padding lines between statements.'
 ---
 
+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/padding-line-between-statements** for documentation.