xo 0.46.4 → 0.49.0

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-boolean-literal-compare.md

@@ -1,4 +1,6 @@
-# Flags unnecessary equality comparisons against boolean literals (`no-unnecessary-boolean-literal-compare`)
+# `no-unnecessary-boolean-literal-compare`
+
+Flags unnecessary equality comparisons against boolean literals.
 
 Comparing boolean values to boolean literals is unnecessary, those comparisons result in the same booleans. Using the boolean values directly, or via a unary negation (`!value`), is more concise and clearer.
 
@@ -18,7 +20,11 @@ distinguish between strict and loose equality. Any example below that uses
 `===` would be treated the same way if `==` was used, and any example below
 that uses `!==` would be treated the same way if `!=` was used.
 
-Examples of **incorrect** code for this rule:
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 declare const someCondition: boolean;
@@ -26,7 +32,7 @@ if (someCondition === true) {
 }
 ```
 
-Examples of **correct** code for this rule
+### ✅ Correct
 
 ```ts
 declare const someCondition: boolean;
@@ -70,7 +76,11 @@ const defaults = {
 
 ### `allowComparingNullableBooleansToTrue`
 
-Examples of **incorrect** code for this rule with `{ allowComparingNullableBooleansToTrue: false }`:
+Examples of code for this rule with `{ allowComparingNullableBooleansToTrue: false }`:
+
+<!--tabs-->
+
+#### ❌ Incorrect
 
 ```ts
 declare const someUndefinedCondition: boolean | undefined;
@@ -82,7 +92,7 @@ if (someNullCondition !== true) {
 }
 ```
 
-Examples of **correct** code for this rule with `{ allowComparingNullableBooleansToTrue: false }`:
+#### ✅ Correct
 
 ```ts
 declare const someUndefinedCondition: boolean | undefined;
@@ -96,7 +106,11 @@ if (!someNullCondition) {
 
 ### `allowComparingNullableBooleansToFalse`
 
-Examples of **incorrect** code for this rule with `{ allowComparingNullableBooleansToFalse: false }`:
+Examples of code for this rule with `{ allowComparingNullableBooleansToFalse: false }`:
+
+<!--tabs-->
+
+#### ❌ Incorrect
 
 ```ts
 declare const someUndefinedCondition: boolean | undefined;
@@ -108,7 +122,7 @@ if (someNullCondition !== false) {
 }
 ```
 
-Examples of **correct** code for this rule with `{ allowComparingNullableBooleansToFalse: false }`:
+#### ✅ Correct
 
 ```ts
 declare const someUndefinedCondition: boolean | undefined;
@@ -133,12 +147,14 @@ if (!(someNullCondition ?? true)) {
 | `nullableBooleanVar === false` | `nullableBooleanVar ?? true`    | Only checked/fixed if the `allowComparingNullableBooleansToFalse` option is `false` |
 | `nullableBooleanVar !== false` | `!(nullableBooleanVar ?? true)` | Only checked/fixed if the `allowComparingNullableBooleansToFalse` option is `false` |
 
-## Related to
+## Related To
 
 - TSLint: [no-boolean-literal-compare](https://palantir.github.io/tslint/rules/no-boolean-literal-compare)
 
 ## Attributes
 
-- [ ] ✅ Recommended
+- Configs:
+  - [ ] ✅ Recommended
+  - [x] 🔒 Strict
 - [x] 🔧 Fixable
 - [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-condition.md

@@ -1,4 +1,6 @@
-# Prevents conditionals where the type is always truthy or always falsy (`no-unnecessary-condition`)
+# `no-unnecessary-condition`
+
+Prevents conditionals where the type is always truthy or always falsy.
 
 Any expression being used as a condition must be able to evaluate as truthy or falsy in order to be considered "necessary". Conversely, any expression that always evaluates to truthy or always evaluates to falsy, as determined by the type of the expression, is considered unnecessary and will be flagged by this rule.
 
@@ -8,7 +10,13 @@ The following expressions are checked:
 - Conditions for `if`, `for`, `while`, and `do-while` statements
 - Base values of optional chain expressions
 
-Examples of **incorrect** code for this rule:
+## Rule Details
+
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 function head<T>(items: T[]) {
@@ -36,7 +44,7 @@ function bar<T>(arg: string) {
 ].filter(t => t); // number[] is always truthy
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 function head<T>(items: T[]) {
@@ -103,11 +111,12 @@ The main downside to using this rule is the need for type information.
 ## 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.
 
 ## Attributes
 
-- [ ] ✅ Recommended
+- Configs:
+  - [ ] ✅ Recommended
+  - [x] 🔒 Strict
 - [x] 🔧 Fixable
 - [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-qualifier.md

@@ -1,11 +1,17 @@
-# Warns when a namespace qualifier is unnecessary (`no-unnecessary-qualifier`)
+# `no-unnecessary-qualifier`
+
+Warns when a namespace qualifier is unnecessary.
 
 ## Rule Details
 
 This rule aims to let users know when a namespace or enum qualifier is unnecessary,
 whether used for a type or for a value.
 
-Examples of **incorrect** code for this rule:
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 namespace A {
@@ -37,7 +43,7 @@ namespace A {
 }
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 namespace X {
@@ -70,16 +76,31 @@ namespace X {
 }
 ```
 
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-unnecessary-qualifier": "warn"
+  }
+}
+```
+
+This rule is not configurable.
+
 ## When Not To Use It
 
 If you don't care about having unneeded namespace or enum qualifiers, then you don't need to use this rule.
 
-## Further Reading
+## Related To
 
 - TSLint: [no-unnecessary-qualifier](https://palantir.github.io/tslint/rules/no-unnecessary-qualifier/)
 
 ## Attributes
 
-- [ ] ✅ Recommended
+- Configs:
+  - [ ] ✅ Recommended
+  - [ ] 🔒 Strict
 - [x] 🔧 Fixable
 - [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-type-arguments.md

@@ -1,4 +1,6 @@
-# Enforces that type arguments will not be used if not required (`no-unnecessary-type-arguments`)
+# `no-unnecessary-type-arguments`
+
+Enforces that type arguments will not be used if not required.
 
 Warns if an explicitly specified type argument is the default for that type parameter.
 
@@ -13,7 +15,11 @@ function f<T = number>() {}
 
 It is redundant to provide an explicit type parameter equal to that default.
 
-Examples of **incorrect** code for this rule:
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 function f<T = number>() {}
@@ -31,7 +37,7 @@ interface I<T = number> {}
 class Impl implements I<number> {}
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 function f<T = number>() {}
@@ -48,12 +54,27 @@ interface I<T = number> {}
 class Impl implements I<string> {}
 ```
 
-## Related to
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-unnecessary-type-arguments": "warn"
+  }
+}
+```
+
+This rule is not configurable.
+
+## Related To
 
 - TSLint: [use-default-type-parameter](https://palantir.github.io/tslint/rules/use-default-type-parameter)
 
 ## Attributes
 
-- [ ] ✅ Recommended
+- Configs:
+  - [ ] ✅ Recommended
+  - [x] 🔒 Strict
 - [x] 🔧 Fixable
 - [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-type-assertion.md

@@ -1,4 +1,6 @@
-# Warns if a type assertion does not change the type of an expression (`no-unnecessary-type-assertion`)
+# `no-unnecessary-type-assertion`
+
+Warns if a type assertion does not change the type of an expression.
 
 This rule prohibits using a type assertion that does not change the type of an expression.
 
@@ -6,7 +8,11 @@ This rule prohibits using a type assertion that does not change the type of an e
 
 This rule aims to prevent unnecessary type assertions.
 
-Examples of **incorrect** code for this rule:
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 const foo = 3;
@@ -33,7 +39,7 @@ function foo(x: number): number {
 }
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 const foo = <number>3;
@@ -53,7 +59,7 @@ function foo(x: number | undefined): number {
 }
 ```
 
-### Options
+## Options
 
 This rule optionally takes an object with a single property `typesToIgnore`, which can be set to a list of type names to ignore.
 
@@ -68,12 +74,14 @@ const foo: Foo = 3;
 
 If you don't care about having no-op type assertions in your code, then you can turn off this rule.
 
-## Related to
+## Related To
 
 - TSLint: [`no-unnecessary-type-assertion`](https://palantir.github.io/tslint/rules/no-unnecessary-type-assertion/)
 
 ## Attributes
 
-- [x] ✅ Recommended
+- Configs:
+  - [x] ✅ Recommended
+  - [x] 🔒 Strict
 - [x] 🔧 Fixable
 - [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-type-constraint.md

@@ -1,4 +1,6 @@
-# Disallows unnecessary constraints on generic types (`no-unnecessary-type-constraint`)
+# `no-unnecessary-type-constraint`
+
+Disallows unnecessary constraints on generic types.
 
 ## Rule Details
 
@@ -10,7 +12,11 @@ When not provided, type parameters happen to default to:
 
 It is therefore redundant to `extend` from these types in later versions of TypeScript.
 
-Examples of **incorrect** code for this rule:
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 interface FooAny<T extends any> {}
@@ -34,7 +40,7 @@ function QuuzAny<T extends any>() {}
 function QuuzUnknown<T extends unknown>() {}
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 interface Foo<T> {}
@@ -50,12 +56,27 @@ const Quux = <T>() => {};
 function Quuz<T>() {}
 ```
 
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-unnecessary-type-constraint": "error"
+  }
+}
+```
+
+This rule is not configurable.
+
 ## 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.
 
 ## Attributes
 
-- [x] ✅ Recommended
-- [x] 🔧 Fixable
+- Configs:
+  - [x] ✅ Recommended
+  - [x] 🔒 Strict
+- [ ] 🔧 Fixable
 - [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unsafe-argument.md

@@ -1,4 +1,6 @@
-# Disallows calling a function with an any type value (`no-unsafe-argument`)
+# `no-unsafe-argument`
+
+Disallows calling a function with an any type value.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 Call a function with `any` typed argument are not checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -9,10 +11,14 @@ This rule disallows calling a function with `any` in its arguments, and it will
 This rule also disallows spreading a tuple type with one of its elements typed as `any`.
 This rule also compares the argument's type to the variable's type to ensure you don't pass an unsafe `any` in a generic position to a receiver that's expecting a specific type. For example, it will error if you assign `Set<any>` to an argument declared as `Set<string>`.
 
-Examples of **incorrect** code for this rule:
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
-declare function foo(arg1: string, arg2: number, arg2: string): void;
+declare function foo(arg1: string, arg2: number, arg3: string): void;
 
 const anyTyped = 1 as any;
 
@@ -36,10 +42,10 @@ declare function baz(arg1: Set<string>, arg2: Map<string, string>): void;
 foo(new Set<any>(), new Map<any, string>());
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
-declare function foo(arg1: string, arg2: number, arg2: string): void;
+declare function foo(arg1: string, arg2: number, arg3: string): void;
 
 foo('a', 1, 'b');
 
@@ -54,6 +60,8 @@ declare function baz(arg1: Set<string>, arg2: Map<string, string>): void;
 foo(new Set<string>(), new Map<string, string>());
 ```
 
+<!--/tabs-->
+
 There are cases where the rule allows passing an argument of `any` to `unknown`.
 
 Example of `any` to `unknown` assignment that are allowed.
@@ -63,13 +71,28 @@ declare function foo(arg1: unknown, arg2: Set<unkown>, arg3: unknown[]): void;
 foo(1 as any, new Set<any>(), [] as any[]);
 ```
 
-## Related to
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-unsafe-argument": "error"
+  }
+}
+```
+
+This rule is not configurable.
+
+## Related To
 
 - [`no-explicit-any`](./no-explicit-any.md)
 - TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)
 
 ## Attributes
 
-- [x] ✅ Recommended
+- Configs:
+  - [x] ✅ Recommended
+  - [x] 🔒 Strict
 - [ ] 🔧 Fixable
 - [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unsafe-assignment.md

@@ -1,4 +1,6 @@
-# Disallows assigning any to variables and properties (`no-unsafe-assignment`)
+# `no-unsafe-assignment`
+
+Disallows assigning any to variables and properties.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 Assigning an `any` typed value to a variable can be hard to pick up on, particularly if it leaks in from an external library. Operations on the variable will not be checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -8,7 +10,11 @@ Assigning an `any` typed value to a variable can be hard to pick up on, particul
 This rule disallows assigning `any` to a variable, and assigning `any[]` to an array destructuring.
 This rule also compares the assigned type to the variable's type to ensure you don't assign an unsafe `any` in a generic position to a receiver that's expecting a specific type. For example, it will error if you assign `Set<any>` to a variable declared as `Set<string>`.
 
-Examples of **incorrect** code for this rule:
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 const x = 1 as any,
@@ -33,7 +39,7 @@ const x: Set<string[]> = new Set<any[]>();
 const x: Set<Set<Set<string>>> = new Set<Set<Set<any>>>();
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 const x = 1,
@@ -56,6 +62,8 @@ const x: Set<string[]> = new Set<string[]>();
 const x: Set<Set<Set<string>>> = new Set<Set<Set<string>>>();
 ```
 
+<!--/tabs-->
+
 There are cases where the rule allows assignment of `any` to `unknown`.
 
 Example of `any` to `unknown` assignment that are allowed.
@@ -66,13 +74,28 @@ const x: unknown[] = y as any[];
 const x: Set<unknown> = y as Set<any>;
 ```
 
-## Related to
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-unsafe-assignment": "error"
+  }
+}
+```
+
+This rule is not configurable.
+
+## Related To
 
 - [`no-explicit-any`](./no-explicit-any.md)
 - TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)
 
 ## Attributes
 
-- [x] ✅ Recommended
+- Configs:
+  - [x] ✅ Recommended
+  - [x] 🔒 Strict
 - [ ] 🔧 Fixable
 - [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unsafe-call.md

@@ -1,4 +1,6 @@
-# Disallows calling an any type value (`no-unsafe-call`)
+# `no-unsafe-call`
+
+Disallows calling an any type value.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 The arguments to, and return value of calling an `any` typed variable are not checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -7,7 +9,11 @@ The arguments to, and return value of calling an `any` typed variable are not ch
 
 This rule disallows calling any variable that is typed as `any`.
 
-Examples of **incorrect** code for this rule:
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 declare const anyVar: any;
@@ -26,7 +32,7 @@ anyVar`foo`;
 nestedAny.prop`foo`;
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 declare const typedVar: () => void;
@@ -42,13 +48,28 @@ new Map();
 String.raw`foo`;
 ```
 
-## Related to
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-unsafe-call": "error"
+  }
+}
+```
+
+This rule is not configurable.
+
+## Related To
 
 - [`no-explicit-any`](./no-explicit-any.md)
 - TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)
 
 ## Attributes
 
-- [x] ✅ Recommended
+- Configs:
+  - [x] ✅ Recommended
+  - [x] 🔒 Strict
 - [ ] 🔧 Fixable
 - [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unsafe-member-access.md

@@ -1,4 +1,6 @@
-# Disallows member access on any typed variables (`no-unsafe-member-access`)
+# `no-unsafe-member-access`
+
+Disallows member access on any typed variables.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 Member access on `any` typed variables is not checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -7,7 +9,11 @@ Member access on `any` typed variables is not checked at all by TypeScript, so i
 
 This rule disallows member access on any variable that is typed as `any`.
 
-Examples of **incorrect** code for this rule:
+Examples of code for this rule:
+
+<!--tabs-->
+
+### ❌ Incorrect
 
 ```ts
 declare const anyVar: any;
@@ -30,7 +36,7 @@ arr[anyVar];
 nestedAny[anyVar];
 ```
 
-Examples of **correct** code for this rule:
+### ✅ Correct
 
 ```ts
 declare const properlyTyped: { prop: { a: string } };
@@ -48,13 +54,28 @@ arr[idx];
 arr[idx++];
 ```
 
-## Related to
+## Options
+
+```jsonc
+// .eslintrc.json
+{
+  "rules": {
+    "@typescript-eslint/no-unsafe-member-access": "error"
+  }
+}
+```
+
+This rule is not configurable.
+
+## Related To
 
 - [`no-explicit-any`](./no-explicit-any.md)
 - TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)
 
 ## Attributes
 
-- [x] ✅ Recommended
+- Configs:
+  - [x] ✅ Recommended
+  - [x] 🔒 Strict
 - [ ] 🔧 Fixable
 - [x] 💭 Requires type information