Description
Overview
Splitting out of #8700: ban-types has long been a kind of mirror to the core ESLint rule no-restricted-syntax. But, ban-types also comes with some default settings. That means the rule really has two areas of responsibility:
- Banning confusing built-in types
- Giving users the ability to ban types of their choosing
That dual-responsibility has led to the rule being more convoluted to configure than average. It's the only rule of ours right now that has to include an extendDefaults option.
Once #8977 is in, the defaults for ban-types will exclusively target the uppercase aliases of primitive types (Boolean, Number, ...) and the general Function and Object types. I think the v8 breaking changes are a good opportunity to further simplify the rule. Proposal: let's...
- Remove the remaining default options for
ban-types, rename it tono-restricted-types(to mirrorno-restricted-syntax), and remove it fromrecommended - Add 1-3 new rule(s) in
recommendedthat ban those previous default types- Starting proposal: a single
no-uppercase-alias-typesrule?
- Starting proposal: a single
This would be a breaking change in that it would change the defaults for ban-types. Note that the stuff linted against by default in ban-types would still be linted against - just by different rule(s).