xo 0.49.0 → 0.50.0

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-misused-promises.md

@@ -1,6 +1,6 @@
 # `no-misused-promises`
 
-Avoid using Promises in places not designed to handle them.
+Disallows Promises in places not designed to handle them.
 
 This rule forbids providing Promises to logical locations such as if statements in places where the TypeScript compiler allows them but they are not handled properly.
 These situations can often arise due to a missing `await` keyword or just a misunderstanding of the way async
@@ -13,9 +13,9 @@ See [`no-floating-promises`](./no-floating-promises.md) for detecting unhandled
 
 ## Rule Details
 
-This rule accepts a single option which is an object with `checksConditionals`
-and `checksVoidReturn` properties indicating which types of misuse to flag.
-Both are enabled by default.
+This rule accepts a single option which is an object with `checksConditionals`,
+`checksVoidReturn`, and `checksSpreads` properties indicating which types of
+misuse to flag. All are enabled by default.
 
 ## Options
 
@@ -24,6 +24,7 @@ type Options = [
   {
     checksConditionals?: boolean;
     checksVoidReturn?: boolean | ChecksVoidReturnOptions;
+    checksSpreads?: boolean;
   },
 ];
 
@@ -39,6 +40,7 @@ const defaultOptions: Options = [
   {
     checksConditionals: true,
     checksVoidReturn: true,
+    checksSpreads: true,
   },
 ];
 ```
@@ -101,6 +103,21 @@ For example, if you don't mind that passing a `() => Promise<void>` to a `() =>
 }
 ```
 
+### `"checksSpreads"`
+
+If you don't want to check object spreads, you can add this configuration:
+
+```json
+{
+  "@typescript-eslint/no-misused-promises": [
+    "error",
+    {
+      "checksSpreads": false
+    }
+  ]
+}
+```
+
 ### `checksConditionals: true`
 
 Examples of code for this rule with `checksConditionals: true`:
@@ -212,6 +229,42 @@ eventEmitter.on('some-event', () => {
 
 <!--/tabs-->
 
+### `checksSpreads: true`
+
+Examples of code for this rule with `checksSpreads: true`:
+
+<!--tabs-->
+
+#### ❌ Incorrect
+
+```ts
+const getData = () => someAsyncOperation({ myArg: 'foo' });
+
+return { foo: 42, ...getData() };
+
+const getData2 = async () => {
+  await someAsyncOperation({ myArg: 'foo' });
+};
+
+return { foo: 42, ...getData2() };
+```
+
+#### ✅ Correct
+
+```ts
+const getData = () => someAsyncOperation({ myArg: 'foo' });
+
+return { foo: 42, ...(await getData()) };
+
+const getData2 = async () => {
+  await someAsyncOperation({ myArg: 'foo' });
+};
+
+return { foo: 42, ...(await getData2()) };
+```
+
+<!--tabs-->
+
 ## When Not To Use It
 
 If you do not use Promises in your codebase or are not concerned with possible
@@ -224,11 +277,3 @@ misuses of them outside of what the TypeScript compiler will check.
 ## Related To
 
 - [`no-floating-promises`](./no-floating-promises.md)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-namespace`
 
-Disallow the use of custom TypeScript modules and namespaces.
+Disallows custom TypeScript modules and namespaces.
 
 Custom TypeScript modules (`module foo {}`) and namespaces (`namespace foo {}`) are considered outdated
 ways to organize TypeScript code. ES2015 module syntax is now preferred (`import`/`export`).
@@ -135,11 +135,3 @@ If you are using the ES2015 module syntax, then you will not need this rule.
 ## Related To
 
 - TSLint: [no-namespace](https://palantir.github.io/tslint/rules/no-namespace/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-non-null-asserted-nullish-coalescing.md

@@ -1,6 +1,6 @@
 # `no-non-null-asserted-nullish-coalescing`
 
-Disallows using a non-null assertion in the left operand of the nullish coalescing operator.
+Disallows non-null assertions in the left operand of a nullish coalescing operator.
 
 ## Rule Details
 
@@ -66,11 +66,3 @@ If you are not using TypeScript 3.7 (or greater), then you will not need to use
 
 - [TypeScript 3.7 Release Notes](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-7.html)
 - [Nullish Coalescing Proposal](https://github.com/tc39/proposal-nullish-coalescing)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-non-null-asserted-optional-chain.md

@@ -1,6 +1,6 @@
 # `no-non-null-asserted-optional-chain`
 
-Disallows using a non-null assertion after an optional chain expression.
+Disallows non-null assertions after an optional chain expression.
 
 ## Rule Details
 
@@ -65,11 +65,3 @@ If you are not using TypeScript 3.7 (or greater), then you will not need to use
 
 - [TypeScript 3.7 Release Notes](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-7.html)
 - [Optional Chaining Proposal](https://github.com/tc39/proposal-optional-chaining/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-non-null-assertion.md

@@ -52,11 +52,3 @@ If you don't care about strict null-checking, then you will not need this rule.
 ## Further Reading
 
 - [`no-non-null-assertion`](https://palantir.github.io/tslint/rules/no-non-null-assertion/) in [TSLint](https://palantir.github.io/tslint/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-parameter-properties.md

@@ -1,6 +1,6 @@
 # `no-parameter-properties`
 
-Disallow the use of parameter properties in class constructors.
+Disallows the use of parameter properties in class constructors.
 
 Parameter properties can be confusing to those new to TypeScript as they are less explicit than other ways
 of declaring and initializing class members.
@@ -399,11 +399,3 @@ If you don't care about the using parameter properties in constructors, then you
 ## Related To
 
 - TSLint: [no-parameter-properties](https://palantir.github.io/tslint/rules/no-parameter-properties/)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-redeclare`
 
-Disallow variable redeclaration.
+Disallows variable redeclaration.
 
 ## Rule Details
 
@@ -84,11 +84,3 @@ const something = 2;
 Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-redeclare.md)
 
 </sup>
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-redundant-type-constituents.md

@@ -1,6 +1,6 @@
 # `no-redundant-type-constituents`
 
-Disallow members of unions and intersections that do nothing or override type information.
+Disallows members of unions and intersections that do nothing or override type information.
 
 ## Rule Details
 
@@ -90,11 +90,3 @@ It also does not provide an auto-fixer just yet.
 - [Intersection Types](https://www.typescriptlang.org/docs/handbook/2/objects.html#intersection-types)
 - [Bottom Types](https://en.wikipedia.org/wiki/Bottom_type)
 - [Top Types](https://en.wikipedia.org/wiki/Top_type)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-require-imports.md

@@ -51,11 +51,3 @@ If you don't care about TypeScript module syntax, then you will not need this ru
 ## Related To
 
 - TSLint: [no-require-imports](https://palantir.github.io/tslint/rules/no-require-imports/)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-restricted-imports.md

@@ -1,6 +1,6 @@
 # `no-restricted-imports`
 
-Disallow specified modules when loaded by `import`.
+Disallows specified modules when loaded by `import`.
 
 ## Rule Details
 
@@ -68,11 +68,3 @@ export type { Foo } from 'import-foo';
 import type baz from 'import-baz';
 export type { Baz } from 'import-baz';
 ```
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-shadow`
 
-Disallow variable declarations from shadowing variables declared in the outer scope.
+Disallows variable declarations from shadowing variables declared in the outer scope.
 
 ## Rule Details
 
@@ -91,11 +91,3 @@ type Func = (test: string) => typeof test;
 Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-shadow.md)
 
 </sup>
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-this-alias.md

@@ -1,6 +1,6 @@
 # `no-this-alias`
 
-Disallow aliasing `this`.
+Disallows aliasing `this`.
 
 This rule prohibits assigning variables to `this`.
 
@@ -60,11 +60,3 @@ If you need to assign `this` to variables, you shouldn’t use this rule.
 ## Related To
 
 - TSLint: [`no-this-assignment`](https://palantir.github.io/tslint/rules/no-this-assignment/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-throw-literal.md

@@ -1,6 +1,6 @@
 # `no-throw-literal`
 
-Disallow throwing literals as exceptions.
+Disallows throwing literals as exceptions.
 
 It is considered good practice to only `throw` the `Error` object itself or an object using the `Error` object as base objects for user-defined exceptions.
 The fundamental benefit of `Error` objects is that they automatically keep track of where they were built and originated.
@@ -116,11 +116,3 @@ throw new CustomError();
 Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-throw-literal.md)
 
 </sup>
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-type-alias`
 
-Disallow the use of type aliases.
+Disallows type aliases.
 
 In TypeScript, type aliases serve three purposes:
 
@@ -118,6 +118,8 @@ type Foo = string | string[];
 
 type Foo = string & string[];
 
+type Foo = `foo-${number}`;
+
 // reference types
 interface Bar {}
 class Baz implements Bar {}
@@ -139,6 +141,8 @@ type Foo = string;
 
 type Foo = string & string[];
 
+type Foo = `foo-${number}`;
+
 // reference types
 interface Bar {}
 class Baz implements Bar {}
@@ -156,6 +160,8 @@ type Foo = 'a' | 'b';
 
 type Foo = string | string[];
 
+type Foo = `a-${number}` | `b-${number}`;
+
 // reference types
 interface Bar {}
 class Baz implements Bar {}
@@ -175,6 +181,8 @@ type Foo = string;
 
 type Foo = string | string[];
 
+type Foo = `a-${number}` | `b-${number}`;
+
 // reference types
 interface Bar {}
 class Baz implements Bar {}
@@ -190,6 +198,8 @@ Examples of **correct** code for the `{ "allowAliases": "in-intersections" }` op
 // primitives
 type Foo = string & string[];
 
+type Foo = `a-${number}` & `b-${number}`;
+
 // reference types
 interface Bar {}
 class Baz implements Bar {}
@@ -205,6 +215,8 @@ type Foo = 'a';
 
 type Foo = string;
 
+type Foo = `foo-${number}`;
+
 // reference types
 interface Bar {}
 class Baz implements Bar {}
@@ -222,6 +234,10 @@ type Foo = string | string[];
 
 type Foo = string & string[];
 
+type Foo = `a-${number}` & `b-${number}`;
+
+type Foo = `a-${number}` | `b-${number}`;
+
 // reference types
 interface Bar {}
 class Baz implements Bar {}
@@ -596,11 +612,3 @@ callback, etc. that would cause the code to be unreadable or impractical.
 ## Related To
 
 - TSLint: [interface-over-type-literal](https://palantir.github.io/tslint/rules/interface-over-type-literal/)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unnecessary-boolean-literal-compare`
 
-Flags unnecessary equality comparisons against boolean literals.
+Disallows 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.
 
@@ -150,11 +150,3 @@ if (!(someNullCondition ?? true)) {
 ## Related To
 
 - TSLint: [no-boolean-literal-compare](https://palantir.github.io/tslint/rules/no-boolean-literal-compare)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [x] 🔒 Strict
-- [x] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unnecessary-condition`
 
-Prevents conditionals where the type is always truthy or always falsy.
+Disallows 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.
 
@@ -112,11 +112,3 @@ The main downside to using this rule is the need for type information.
 
 - 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
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [x] 🔒 Strict
-- [x] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unnecessary-qualifier`
 
-Warns when a namespace qualifier is unnecessary.
+Disallows unnecessary namespace qualifiers.
 
 ## Rule Details
 
@@ -96,11 +96,3 @@ If you don't care about having unneeded namespace or enum qualifiers, then you d
 ## Related To
 
 - TSLint: [no-unnecessary-qualifier](https://palantir.github.io/tslint/rules/no-unnecessary-qualifier/)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [x] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unnecessary-type-arguments`
 
-Enforces that type arguments will not be used if not required.
+Disallows type arguments that are equal to the default.
 
 Warns if an explicitly specified type argument is the default for that type parameter.
 
@@ -70,11 +70,3 @@ This rule is not configurable.
 ## Related To
 
 - TSLint: [use-default-type-parameter](https://palantir.github.io/tslint/rules/use-default-type-parameter)
-
-## Attributes
-
-- 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,6 +1,6 @@
 # `no-unnecessary-type-assertion`
 
-Warns if a type assertion does not change the type of an expression.
+Disallows type assertions that do not change the type of an expression.
 
 This rule prohibits using a type assertion that does not change the type of an expression.
 
@@ -77,11 +77,3 @@ If you don't care about having no-op type assertions in your code, then you can
 ## Related To
 
 - TSLint: [`no-unnecessary-type-assertion`](https://palantir.github.io/tslint/rules/no-unnecessary-type-assertion/)
-
-## Attributes
-
-- 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

@@ -72,11 +72,3 @@ 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
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unsafe-argument`
 
-Disallows calling a function with an any type value.
+Disallows calling a function with a value with type `any`.
 
 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.
@@ -88,11 +88,3 @@ This rule is not configurable.
 
 - [`no-explicit-any`](./no-explicit-any.md)
 - TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unsafe-assignment`
 
-Disallows assigning any to variables and properties.
+Disallows assigning a value with type `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.
@@ -91,11 +91,3 @@ This rule is not configurable.
 
 - [`no-explicit-any`](./no-explicit-any.md)
 - TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unsafe-call`
 
-Disallows calling an any type value.
+Disallows calling a value with type `any`.
 
 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.
@@ -65,11 +65,3 @@ This rule is not configurable.
 
 - [`no-explicit-any`](./no-explicit-any.md)
 - TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)
-
-## Attributes
-
-- 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,6 +1,6 @@
 # `no-unsafe-member-access`
 
-Disallows member access on any typed variables.
+Disallows member access on a value with type `any`.
 
 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.
@@ -71,11 +71,3 @@ This rule is not configurable.
 
 - [`no-explicit-any`](./no-explicit-any.md)
 - TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

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

@@ -1,6 +1,6 @@
 # `no-unsafe-return`
 
-Disallows returning any from a function.
+Disallows returning a value with type `any` from a function.
 
 Despite your best intentions, the `any` type can sometimes leak into your codebase.
 Returned `any` typed values are not checked at all by TypeScript, so it creates a potential safety hole, and source of bugs in your codebase.
@@ -108,11 +108,3 @@ This rule is not configurable.
 
 - [`no-explicit-any`](./no-explicit-any.md)
 - TSLint: [`no-unsafe-any`](https://palantir.github.io/tslint/rules/no-unsafe-any/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unused-expressions.md

@@ -1,6 +1,6 @@
 # `no-unused-expressions`
 
-Disallow unused expressions.
+Disallows unused expressions.
 
 ## Rule Details
 
@@ -26,11 +26,3 @@ See [`eslint/no-unused-expressions` options](https://eslint.org/docs/rules/no-un
 Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/no-unused-expressions.md)
 
 </sup>
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information