Before You File a Proposal Please Confirm You Have Done The Following...

• I havesearched for related issues and found none that match my proposal.
• I haveread the FAQ and my problem is not listed.

Description

I feel like the same reasoning applies as for something likeno-unnecessary-condition. It seems like thestrict-type-checked ruleset is for projects where types can be trusted, and in those projects, it makes sense to forbid any kind of type guard, assertion, or really any code that only affects types which can be removed without causing a ts error, and that clearly includes this rule.

Impacted Configurations

Juststrict-type-checked, I believe.

Additional Info

I proposed/helped write the rule, so I'm of course biased.

I don't know the considerations for adding a rule to a preset configuration, but assuming risk is a factor, I think that even though the rule is only a couple of months old, it is based heavily on existing code, I have been using it myself without issues, and there has only been one minor bug report for it (#11192), so it seems safe.