@typescript-eslint/eslint-plugin 8.33.1-alpha.5 → 8.33.1

package/docs/rules/non-nullable-type-assertion-style.mdx

@@ -1,47 +0,0 @@
----
-description: 'Enforce non-null assertions over explicit type assertions.'
----
-
-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.
-
-There are two common ways to assert to TypeScript that a value is its type without `null` or `undefined`:
-
-- `!`: Non-null assertion
-- `as`: Traditional type assertion with a coincidentally equivalent type
-
-`!` non-null assertions are generally preferred for requiring less code and being harder to fall out of sync as types change.
-This rule reports when an `as` assertion is doing the same job as a `!` would, and suggests fixing the code to be an `!`.
-
-## Examples
-
-<Tabs>
-<TabItem value="❌ Incorrect">
-
-```ts
-const maybe: string | undefined = Math.random() > 0.5 ? '' : undefined;
-
-const definitely = maybe as string;
-const alsoDefinitely = <string>maybe;
-```
-
-</TabItem>
-<TabItem value="✅ Correct">
-
-```ts
-const maybe: string | undefined = Math.random() > 0.5 ? '' : undefined;
-
-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

@@ -1,15 +0,0 @@
----
-displayed_sidebar: rulesSidebar
----
-
-:::danger Deprecated
-
-This rule has been moved to the [ESLint stylistic plugin](https://eslint.style).
-See [#8072](https://github.com/typescript-eslint/typescript-eslint/issues/8072) and [#8074](https://github.com/typescript-eslint/typescript-eslint/issues/8074) for more information.
-
-:::
-
-<!-- This doc file has been left on purpose to help direct people to the stylistic plugin.
-
-Note that there is no actual way to get to this page in the normal navigation,
-so end-users will only be able to get to this page from the search bar. -->

package/docs/rules/only-throw-error.mdx

@@ -1,150 +0,0 @@
----
-description: 'Disallow throwing non-`Error` values 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/only-throw-error** for documentation.
-
-It uses type information to determine which values are `Error`s.
-
-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.
-
-:::info[Migration from `no-throw-literal`]
-
-This extension rule was formerly known as `@typescript-eslint/no-throw-literal`.
-The new name is a drop-in replacement with identical functionality.
-
-:::
-
-## Examples
-
-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>
-<TabItem value="❌ Incorrect">
-
-```ts
-throw 'error';
-
-throw 0;
-
-throw undefined;
-
-throw null;
-
-const err = new Error();
-throw 'an ' + err;
-
-const err = new Error();
-throw `${err}`;
-
-const err = '';
-throw err;
-
-function getError() {
-  return '';
-}
-throw getError();
-
-const foo = {
-  bar: '',
-};
-throw foo.bar;
-```
-
-</TabItem>
-<TabItem value="✅ Correct">
-
-```ts
-throw new Error();
-
-throw new Error('error');
-
-const e = new Error('error');
-throw e;
-
-try {
-  throw new Error('error');
-} catch (e) {
-  throw e;
-}
-
-const err = new Error();
-throw err;
-
-function getError() {
-  return new Error();
-}
-throw getError();
-
-const foo = {
-  bar: new Error(),
-};
-throw foo.bar;
-
-class CustomError extends Error {
-  // ...
-}
-throw new CustomError();
-```
-
-</TabItem>
-</Tabs>
-
-## Options
-
-This rule adds the following options:
-
-```ts
-interface Options {
-  /**
-   * Type specifiers that can be thrown.
-   */
-  allow?: (
-    | {
-        from: 'file';
-        name: [string, ...string[]] | string;
-        path?: string;
-      }
-    | {
-        from: 'lib';
-        name: [string, ...string[]] | string;
-      }
-    | {
-        from: 'package';
-        name: [string, ...string[]] | string;
-        package: string;
-      }
-    | string
-  )[];
-
-  /**
-   * Whether to allow rethrowing caught values that are not `Error` objects.
-   */
-  allowRethrowing?: boolean;
-
-  /**
-   * Whether to always allow throwing values typed as `any`.
-   */
-  allowThrowingAny?: boolean;
-
-  /**
-   * Whether to always allow throwing values typed as `unknown`.
-   */
-  allowThrowingUnknown?: boolean;
-}
-
-const defaultOptions: Options = {
-  allow: [],
-  allowRethrowing: false,
-  allowThrowingAny: true,
-  allowThrowingUnknown: true,
-};
-```
-
-{/* Intentionally Omitted: When Not To Use It */}

package/docs/rules/padding-line-between-statements.md

@@ -1,15 +0,0 @@
----
-displayed_sidebar: rulesSidebar
----
-
-:::danger Deprecated
-
-This rule has been moved to the [ESLint stylistic plugin](https://eslint.style).
-See [#8072](https://github.com/typescript-eslint/typescript-eslint/issues/8072) and [#8074](https://github.com/typescript-eslint/typescript-eslint/issues/8074) for more information.
-
-:::
-
-<!-- This doc file has been left on purpose to help direct people to the stylistic plugin.
-
-Note that there is no actual way to get to this page in the normal navigation,
-so end-users will only be able to get to this page from the search bar. -->