@typescript-eslint/eslint-plugin 8.3.1-alpha.5 → 8.3.1-alpha.7

package/docs/rules/prefer-literal-enum-member.mdx

@@ -67,7 +67,7 @@ enum Valid {
 
 ### `allowBitwiseExpressions`
 
-When set to `true` will allow you to use bitwise expressions in enum initializer (default: `false`).
+Whether to allow using bitwise expressions in enum initializers (default: `false`).
 
 Examples of code for the `{ "allowBitwiseExpressions": true }` option:
 

package/docs/rules/prefer-nullish-coalescing.mdx

@@ -25,7 +25,7 @@ This rule will not work as expected if [`strictNullChecks`](https://www.typescri
 
 ### `ignoreTernaryTests`
 
-Setting this option to `true` will cause the rule to ignore any ternary expressions that could be simplified by using the nullish coalescing operator. This is set to `false` by default.
+Whether to ignore any ternary expressions that could be simplified by using the nullish coalescing operator. This is set to `false` by default.
 
 Incorrect code for `ignoreTernaryTests: false`, and correct code for `ignoreTernaryTests: true`:
 
@@ -65,7 +65,7 @@ foo ?? 'a string';
 
 ### `ignoreConditionalTests`
 
-Setting this option to `false` will cause the rule to also check cases that are located within a conditional test. This is set to `true` by default.
+Whether to ignore cases that are located within a conditional test. This is set to `true` by default.
 
 Generally expressions within conditional tests intentionally use the falsy fallthrough behavior of the logical or operator, meaning that fixing the operator to the nullish coalesce operator could cause bugs.
 
@@ -107,7 +107,7 @@ a ?? b ? true : false;
 
 ### `ignoreMixedLogicalExpressions`
 
-Setting this option to `true` will cause the rule to ignore any logical or expressions that are part of a mixed logical expression (with `&&`). This is set to `false` by default.
+Whether to ignore any logical or expressions that are part of a mixed logical expression (with `&&`). This is set to `false` by default.
 
 Generally expressions within mixed logical expressions intentionally use the falsy fallthrough behavior of the logical or operator, meaning that fixing the operator to the nullish coalesce operator could cause bugs.
 
@@ -147,6 +147,8 @@ a ?? (b && c && d);
 
 ### `ignorePrimitives`
 
+Whether to ignore all (`true`) or some (an object with properties) primitive types.
+
 If you would like to ignore expressions containing operands of certain primitive types that can be falsy then you may pass an object containing a boolean value for each primitive:
 
 - `string: true`, ignores `null` or `undefined` unions with `string` (default: false).
@@ -172,7 +174,7 @@ Also, if you would like to ignore all primitives types, you can set `ignorePrimi
 
 ### `allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing`
 
-If this is set to `false`, then the rule will error on every file whose `tsconfig.json` does _not_ have the `strictNullChecks` compiler option (or `strict`) set to `true`.
+Unless this is set to `true`, the rule will error on every file whose `tsconfig.json` does _not_ have the `strictNullChecks` compiler option (or `strict`) set to `true`.
 
 Without `strictNullChecks`, TypeScript essentially erases `undefined` and `null` from the types. This means when this rule inspects the types from a variable, **it will not be able to tell that the variable might be `null` or `undefined`**, which essentially makes this rule useless.
 

package/docs/rules/prefer-readonly-parameter-types.mdx

@@ -140,9 +140,9 @@ interface Foo {
 
 ### `allow`
 
+An array of type specifiers to ignore.
 Some complex types cannot easily be made readonly, for example the `HTMLElement` type or the `JQueryStatic` type from `@types/jquery`. This option allows you to globally disable reporting of such types.
 
-This option takes an array of type specifiers to ignore.
 Each item in the array must have one of the following forms:
 
 - A type defined in a file (`{ from: "file", name: "Foo", path: "src/foo-file.ts" }` with `path` being an optional path relative to the project root directory)
@@ -258,7 +258,7 @@ function fn(arg: Foo) {}
 
 ### `checkParameterProperties`
 
-This option allows you to enable or disable the checking of parameter properties.
+Whether to check class parameter properties.
 Because parameter properties create properties on the class, it may be undesirable to force them to be readonly.
 
 Examples of code for this rule with `{checkParameterProperties: true}`:
@@ -297,7 +297,8 @@ class Foo {
 
 ### `ignoreInferredTypes`
 
-This option allows you to ignore parameters which don't explicitly specify a type. This may be desirable in cases where an external dependency specifies a callback with mutable parameters, and manually annotating the callback's parameters is undesirable.
+Whether to ignore parameters which don't explicitly specify a type.
+This may be desirable in cases where an external dependency specifies a callback with mutable parameters, and manually annotating the callback's parameters is undesirable.
 
 Examples of code for this rule with `{ignoreInferredTypes: true}`:
 
@@ -354,7 +355,8 @@ export const acceptsCallback: AcceptsCallback;
 
 ### `treatMethodsAsReadonly`
 
-This option allows you to treat all mutable methods as though they were readonly. This may be desirable when you are never reassigning methods.
+Whether to treat all mutable methods as though they are readonly.
+This may be desirable when you are never reassigning methods.
 
 Examples of code for this rule with `{treatMethodsAsReadonly: false}`:
 

package/docs/rules/promise-function-async.mdx

@@ -68,7 +68,7 @@ async function functionReturnsUnionWithPromiseImplicitly(p: boolean) {
 
 ### `allowAny`
 
-Whether to ignore functions that return `any` and `unknown`.
+Whether to ignore functions that return `any` or `unknown`.
 If you want additional safety, consider turning this option off, as it makes the rule less able to catch incorrect Promise behaviors.
 
 Examples of code with `{ "allowAny": false }`:
@@ -135,7 +135,7 @@ Whether to check inline function expressions.
 
 ### `checkMethodDeclarations`
 
-Whether to check methods on classes and object literals
+Whether to check methods on classes and object literals.
 `true` by default, but can be set to `false` to ignore them.
 
 ## When Not To Use It

package/docs/rules/typedef.mdx

@@ -306,7 +306,7 @@ let delayedText: string;
 
 ### `variableDeclarationIgnoreFunction`
 
-Ignore variable declarations for non-arrow and arrow functions.
+Whether to ignore variable declarations for non-arrow and arrow functions.
 
 Examples of code with `{ "variableDeclaration": true, "variableDeclarationIgnoreFunction": true }`:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typescript-eslint/eslint-plugin",
-  "version": "8.3.1-alpha.5",
+  "version": "8.3.1-alpha.7",
   "description": "TypeScript plugin for ESLint",
   "files": [
     "dist",
@@ -60,10 +60,10 @@
   },
   "dependencies": {
     "@eslint-community/regexpp": "^4.10.0",
-    "@typescript-eslint/scope-manager": "8.3.1-alpha.5",
-    "@typescript-eslint/type-utils": "8.3.1-alpha.5",
-    "@typescript-eslint/utils": "8.3.1-alpha.5",
-    "@typescript-eslint/visitor-keys": "8.3.1-alpha.5",
+    "@typescript-eslint/scope-manager": "8.3.1-alpha.7",
+    "@typescript-eslint/type-utils": "8.3.1-alpha.7",
+    "@typescript-eslint/utils": "8.3.1-alpha.7",
+    "@typescript-eslint/visitor-keys": "8.3.1-alpha.7",
     "graphemer": "^1.4.0",
     "ignore": "^5.3.1",
     "natural-compare": "^1.4.0",
@@ -74,8 +74,8 @@
     "@types/marked": "^5.0.2",
     "@types/mdast": "^4.0.3",
     "@types/natural-compare": "*",
-    "@typescript-eslint/rule-schema-to-typescript-types": "8.3.1-alpha.5",
-    "@typescript-eslint/rule-tester": "8.3.1-alpha.5",
+    "@typescript-eslint/rule-schema-to-typescript-types": "8.3.1-alpha.7",
+    "@typescript-eslint/rule-tester": "8.3.1-alpha.7",
     "ajv": "^6.12.6",
     "cross-env": "^7.0.3",
     "cross-fetch": "*",