Overview

An option named allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing exists in three rules:

• no-unnecessary-condition
• prefer-nullish-coalescing
• strict-boolean-expressions

Each comes with a very stern explanation of why not to use it:

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 a lot less useful.

It's bugged me for a while that we've kept these options around. They add bloat to the docs and rule logic. And practically nobody uses them.

A Sourcegraph search for allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing shows only 3 public repos visibly using setting it to true - and 5 setting it to false.

Proposal: let's...

1. Deprecate the options as a non-breaking change now
2. Remove them in the next major version with functional changes

💖