Overview

Splitting out of#8700:ban-types has long been a kind of mirror to the core ESLint ruleno-restricted-syntax. But,ban-typesalso 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 anextendDefaults option.

Once#8977 is in, the defaults forban-types will exclusively target the uppercase aliases of primitive types (Boolean,Number, ...) and the generalFunction andObject types. I think the v8 breaking changes are a good opportunity to further simplify the rule. Proposal: let's...

• Remove the remaining default options forban-types, rename it tono-restricted-types (to mirrorno-restricted-syntax), and remove it fromrecommended
• Add 1-3 new rule(s) inrecommended that ban those previous default types
  • Starting proposal: a singleno-uppercase-alias-types rule?

This would be a breaking change in that it would change the defaults forban-types. Note that the stuff linted against by default inban-types would still be linted against - just by different rule(s).