@typescript-eslint/eslint-plugin 7.2.1-alpha.2 → 7.2.1-alpha.4

package/docs/rules/{consistent-type-definitions.md → consistent-type-definitions.mdx}

@@ -2,6 +2,9 @@
 description: 'Enforce type definitions to consistently use either `interface` or `type`.'
 ---
 
+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/consistent-type-definitions** for documentation.
@@ -32,15 +35,15 @@ Using the same type declaration style consistently helps with code readability.
 
 ### `interface`
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='"interface"'
 type T = { x: number };
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='"interface"'
 type T = string;
@@ -51,11 +54,13 @@ interface T {
 }
 ```
 
-### `type`
+</TabItem>
+</Tabs>
 
-<!--tabs-->
+### `type`
 
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='"type"'
 interface T {
@@ -63,12 +68,16 @@ interface T {
 }
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='"type"'
 type T = { x: number };
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If you specifically want to use an interface or type literal for stylistic reasons, you can avoid this rule.

package/docs/rules/{consistent-type-exports.md → consistent-type-exports.mdx}

@@ -2,6 +2,9 @@
 description: 'Enforce consistent usage of type exports.'
 ---
 
+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/consistent-type-exports** for documentation.
@@ -13,9 +16,8 @@ This allows transpilers to drop exports without knowing the types of the depende
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 interface ButtonProps {
@@ -29,7 +31,8 @@ class Button implements ButtonProps {
 export { Button, ButtonProps };
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 interface ButtonProps {
@@ -44,6 +47,9 @@ export { Button };
 export type { ButtonProps };
 ```
 
+</TabItem>
+</Tabs>
+
 ## Options
 
 ### `fixMixedExportsWithInlineTypeSpecifier`
@@ -79,21 +85,24 @@ export type { T };
 export { x };
 ```
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "fixMixedExportsWithInlineTypeSpecifier": true }'
 export { Button } from 'some-library';
 export type { ButtonProps } from 'some-library';
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "fixMixedExportsWithInlineTypeSpecifier": true }'
 export { Button, type ButtonProps } from 'some-library';
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If you use `--isolatedModules` the compiler would error if a type is not re-exported using `export type`.

package/docs/rules/{consistent-type-imports.md → consistent-type-imports.mdx}

@@ -2,6 +2,9 @@
 description: 'Enforce consistent usage of type imports.'
 ---
 
+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/consistent-type-imports** for documentation.
@@ -45,9 +48,8 @@ This option defines the expected type modifier to be added when an import is det
 - `separate-type-imports` will add the type keyword after the import keyword `import type { A } from '...'`. It is the default.
 - `inline-type-imports` will inline the type keyword `import { type A } from '...'` and is only available in TypeScript 4.5 and onwards. See [documentation here](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-5.html#type-modifiers-on-import-names 'TypeScript 4.5 documentation on type modifiers and import names').
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 import { Foo } from 'Foo';
@@ -56,7 +58,8 @@ type T = Foo;
 const x: Bar = 1;
 ```
 
-#### ✅ With `separate-type-imports`
+</TabItem>
+<TabItem value="✅ With `separate-type-imports`">
 
 ```ts option='{ "fixStyle": "separate-type-imports" }'
 import type { Foo } from 'Foo';
@@ -65,7 +68,8 @@ type T = Foo;
 const x: Bar = 1;
 ```
 
-#### ✅ With `inline-type-imports`
+</TabItem>
+<TabItem value="✅ With `inline-type-imports`">
 
 ```ts option='{ "fixStyle": "inline-type-imports" }'
 import { type Foo } from 'Foo';
@@ -74,7 +78,8 @@ type T = Foo;
 const x: Bar = 1;
 ```
 
-<!--tabs-->
+</TabItem>
+</Tabs>
 
 ### `disallowTypeAnnotations`
 
@@ -103,6 +108,6 @@ We recommend picking a single option for this rule that works best for your proj
 
 ## Related To
 
-- [`no-import-type-side-effects`](./no-import-type-side-effects.md)
-- [`import/consistent-type-specifier-style`](https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/consistent-type-specifier-style.md)
+- [`no-import-type-side-effects`](./no-import-type-side-effects.mdx)
+- [`import/consistent-type-specifier-style`](https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/consistent-type-specifier-style.mdx)
 - [`import/no-duplicates` with `{"prefer-inline": true}`](https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-duplicates.md#inline-type-imports)

package/docs/rules/{default-param-last.md → default-param-last.mdx}

@@ -2,6 +2,9 @@
 description: 'Enforce default parameters to be last.'
 ---
 
+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/default-param-last** for documentation.
@@ -9,9 +12,8 @@ description: 'Enforce default parameters to be last.'
 This rule extends the base [`eslint/default-param-last`](https://eslint.org/docs/rules/default-param-last) rule.
 It adds support for optional parameters.
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 /* eslint @typescript-eslint/default-param-last: "error" */
@@ -33,7 +35,8 @@ class Foo {
 }
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 /* eslint @typescript-eslint/default-param-last: "error" */
@@ -56,3 +59,6 @@ class Foo {
   ) {}
 }
 ```
+
+</TabItem>
+</Tabs>

package/docs/rules/{dot-notation.md → dot-notation.mdx}

@@ -2,6 +2,9 @@
 description: 'Enforce dot notation whenever possible.'
 ---
 
+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/dot-notation** for documentation.

package/docs/rules/{explicit-function-return-type.md → explicit-function-return-type.mdx}

@@ -2,6 +2,9 @@
 description: 'Require explicit return types on functions and class methods.'
 ---
 
+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/explicit-function-return-type** for documentation.
@@ -16,9 +19,8 @@ This rule enforces that functions do have an explicit return type annotation.
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 // Should indicate that no value is returned (void)
@@ -42,7 +44,8 @@ class Test {
 }
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 // No return value should be expected (void)
@@ -66,6 +69,9 @@ class Test {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ## Options
 
 ### Configuring in a mixed JS/TS codebase
@@ -94,9 +100,8 @@ If you are working on a codebase within which you lint non-TypeScript code (i.e.
 
 Examples of code for this rule with `{ allowExpressions: true }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowExpressions": true }'
 function test() {}
@@ -106,7 +111,8 @@ const fn = () => {};
 export default () => {};
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowExpressions": true }'
 node.addEventListener('click', () => {});
@@ -116,13 +122,15 @@ node.addEventListener('click', function () {});
 const foo = arr.map(i => i * i);
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowTypedFunctionExpressions`
 
 Examples of code for this rule with `{ allowTypedFunctionExpressions: true }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowTypedFunctionExpressions": true }'
 let arrowFn = () => 'test';
@@ -136,7 +144,8 @@ let objectProp = {
 };
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowTypedFunctionExpressions": true }'
 type FuncType = () => string;
@@ -174,13 +183,15 @@ functionWithObjectArg({
 });
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowHigherOrderFunctions`
 
 Examples of code for this rule with `{ allowHigherOrderFunctions: true }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowHigherOrderFunctions": true }'
 var arrowFn = () => () => {};
@@ -190,7 +201,8 @@ function fn() {
 }
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowHigherOrderFunctions": true }'
 var arrowFn = () => (): void => {};
@@ -200,33 +212,38 @@ function fn() {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowDirectConstAssertionInArrowFunctions`
 
 Examples of code for this rule with `{ allowDirectConstAssertionInArrowFunctions: true }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowDirectConstAssertionInArrowFunctions": true }'
 const func = (value: number) => ({ type: 'X', value }) as any;
 const func = (value: number) => ({ type: 'X', value }) as Action;
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowDirectConstAssertionInArrowFunctions": true }'
 const func = (value: number) => ({ foo: 'bar', value }) as const;
 const func = () => x as const;
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowConciseArrowFunctionExpressionsStartingWithVoid`
 
 Examples of code for this rule with `{ allowConciseArrowFunctionExpressionsStartingWithVoid: true }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowConciseArrowFunctionExpressionsStartingWithVoid": true }'
 var join = (a: string, b: string) => `${a}${b}`;
@@ -236,19 +253,22 @@ const log = (message: string) => {
 };
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowConciseArrowFunctionExpressionsStartingWithVoid": true }'
 var log = (message: string) => void console.log(message);
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowFunctionsWithoutTypeParameters`
 
 Examples of code for this rule with `{ allowFunctionsWithoutTypeParameters: true }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowFunctionsWithoutTypeParameters": true }'
 function foo<T>(t: T) {
@@ -258,7 +278,8 @@ function foo<T>(t: T) {
 const bar = <T>(t: T) => t;
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowFunctionsWithoutTypeParameters": true }'
 function foo<T>(t: T): T {
@@ -274,6 +295,9 @@ function allowedFunction(x: string) {
 const allowedArrow = (x: string) => x;
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowedNames`
 
 You may pass function/method names you would like this rule to ignore, like so:
@@ -293,15 +317,15 @@ You may pass function/method names you would like this rule to ignore, like so:
 
 Examples of code for this rule with `{ allowIIFEs: true }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowIIFEs": true }'
 var func = () => 'foo';
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowIIFEs": true }'
 var foo = (() => 'foo')();
@@ -311,6 +335,9 @@ var bar = (function () {
 })();
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If you don't find the added cost of explicitly writing function return types to be worth the visual clarity, or your project is not large enough for it to be a factor in type checking performance, then you will not need this rule.

package/docs/rules/{explicit-member-accessibility.md → explicit-member-accessibility.mdx}

@@ -2,6 +2,9 @@
 description: 'Require explicit accessibility modifiers on class properties and methods.'
 ---
 
+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/explicit-member-accessibility** for documentation.

package/docs/rules/{explicit-module-boundary-types.md → explicit-module-boundary-types.mdx}

@@ -2,6 +2,9 @@
 description: "Require explicit return and argument types on exported functions' and classes' public class methods."
 ---
 
+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/explicit-module-boundary-types** for documentation.
@@ -12,9 +15,8 @@ It can also improve TypeScript type checking performance on larger codebases.
 
 ## Examples
 
-<!--tabs-->
-
-### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts
 // Should indicate that no value is returned (void)
@@ -37,7 +39,8 @@ export class Test {
 }
 ```
 
-### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts
 // A function with no return value (void)
@@ -65,6 +68,9 @@ function test() {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ## Options
 
 ### Configuring in a mixed JS/TS codebase
@@ -93,27 +99,29 @@ If you are working on a codebase within which you lint non-TypeScript code (i.e.
 
 Examples of code for this rule with `{ allowArgumentsExplicitlyTypedAsAny: false }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowArgumentsExplicitlyTypedAsAny": false }'
 export const func = (value: any): number => value + 1;
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowArgumentsExplicitlyTypedAsAny": false }'
 export const func = (value: number): number => value + 1;
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowDirectConstAssertionInArrowFunctions`
 
 Examples of code for this rule with `{ allowDirectConstAssertionInArrowFunctions: false }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowArgumentsExplicitlyTypedAsAny": false }'
 export const func = (value: number) => ({ type: 'X', value });
@@ -123,7 +131,8 @@ export const foo = () => ({
 export const bar = () => 1;
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowArgumentsExplicitlyTypedAsAny": false }'
 export const func = (value: number) => ({ type: 'X', value }) as const;
@@ -134,6 +143,9 @@ export const foo = () =>
 export const bar = () => 1 as const;
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowedNames`
 
 You may pass function/method names you would like this rule to ignore, like so:
@@ -153,9 +165,8 @@ You may pass function/method names you would like this rule to ignore, like so:
 
 Examples of code for this rule with `{ allowHigherOrderFunctions: false }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowHigherOrderFunctions": false }'
 export const arrowFn = () => () => {};
@@ -169,7 +180,8 @@ export function foo(outer: string) {
 }
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowHigherOrderFunctions": false }'
 export const arrowFn = () => (): void => {};
@@ -183,13 +195,15 @@ export function foo(outer: string) {
 }
 ```
 
+</TabItem>
+</Tabs>
+
 ### `allowTypedFunctionExpressions`
 
 Examples of code for this rule with `{ allowTypedFunctionExpressions: false }`:
 
-<!--tabs-->
-
-#### ❌ Incorrect
+<Tabs>
+<TabItem value="❌ Incorrect">
 
 ```ts option='{ "allowTypedFunctionExpressions": false }'
 export let arrowFn = () => 'test';
@@ -205,7 +219,8 @@ export let objectProp = {
 export const foo = bar => {};
 ```
 
-#### ✅ Correct
+</TabItem>
+<TabItem value="✅ Correct">
 
 ```ts option='{ "allowTypedFunctionExpressions": false }'
 type FuncType = () => string;
@@ -236,6 +251,9 @@ type FooType = (bar: string) => void;
 export const foo: FooType = bar => {};
 ```
 
+</TabItem>
+</Tabs>
+
 ## When Not To Use It
 
 If your project is not used by downstream consumers that are sensitive to API types, you can disable this rule.
@@ -246,4 +264,4 @@ If your project is not used by downstream consumers that are sensitive to API ty
 
 ## Related To
 
-- [explicit-function-return-type](./explicit-function-return-type.md)
+- [explicit-function-return-type](./explicit-function-return-type.mdx)

package/docs/rules/{func-call-spacing.md → func-call-spacing.mdx}

@@ -2,6 +2,9 @@
 description: 'Require or disallow spacing between function identifiers and their invocations.'
 ---
 
+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/func-call-spacing** for documentation.

package/docs/rules/{indent.md → indent.mdx}

@@ -2,6 +2,9 @@
 description: 'Enforce consistent indentation.'
 ---
 
+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/indent** for documentation.

package/docs/rules/{init-declarations.md → init-declarations.mdx}

@@ -2,6 +2,9 @@
 description: 'Require or disallow initialization in variable declarations.'
 ---
 
+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/init-declarations** for documentation.