Closed 3flex closed 3 weeks ago
Then why it's necessary?
Sorry I don't understand the question?
The type assertions that were removed are not necessary. An ESLint rule is enabled that detects this (and prevents future violations).
Are you asking why the rule needs to be enabled at all?
It's because the recommended type checked rules aren't currently enabled in this project, so I've enabled the rule on its own and fixed the violations.
@3flex And why can't we enable the preset? It's a matter of adding tseslint.configs.strictTypeChecked
and tseslint.configs.stylisticTypeChecked
There are currently hundreds of violations if those rule sets are enabled.
Do you want to enable the rulesets then disable all the rules that have violations? Or add eslint ignore rules to each line that triggers a rule on that ruleset?
I think enabling a few rules at a time until we have all/most of them and then switch to the preset would be preferred so the pull requests are small.
This is enabled by default in the recommended type checked rule set.