8000 docs: [prefer-nullish-coalescing] fix admonition (#10574) · 43081j/typescript-eslint@4e7f5f8 · GitHub
[go: up one dir, main page]

Skip to content

Commit 4e7f5f8

Browse files
docs: [prefer-nullish-coalescing] fix admonition (typescript-eslint#10574)
fixed
1 parent cde2f97 commit 4e7f5f8

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

packages/eslint-plugin/docs/rules/prefer-nullish-coalescing.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -198,13 +198,13 @@ const x = Boolean(a ?? b);
198198

199199
### `allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing`
200200

201-
{/* insert option description */}
202-
203201
:::danger Deprecated
204202

205-
> This option will be removed in the next major version of typescript-eslint.
206-
> :::
207-
> 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`.
203+
This option will be removed in the next major version of typescript-eslint.
204+
205+
:::
206+
207+
{/* insert option description */}
208208

209209
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.
210210

0 commit comments

Comments
 (0)
0