[Bug] It's not enough to just look at the name. If someone happens to redeclare their own class, such asclass Uint8Array<T>, the rule should know to check that:

https://deploy-preview-10477--typescript-eslint.netlify.app/play/#ts=5.7.2&fileType=.ts&code=MYGwhgzhAECqCWA7ALgDgIICdNgJ4B4AVAPmgG8AoaaAehugDomKBfCikAU2WjAC44SNFhwEReAEIBXAGYzOmADLwA1p1IBeaIk4B3QSgzY8ACgCUAbnacAHgAcA9ph5kWQA&eslintrc=N4KABGBEBOCuA2BTAzpAXGUEKQAIBcBPABxQGNoBLY-AWhXkoDt8B6MgeyeUuX0Ra0A5gMRUytTt3xwy%2BDtFQZIY6AsjgwAXxBagA&tsconfig=N4KABGBEDGD2C2AHAlgGwKYCcDyiAuysAdgM6QBcYoEEkqyARhWANqTokBMADJwMyQAugBpwNSPFgATAK4Zm7Lr06RRNKCTyZk0PADk5qAMIALdNADWZSlpno14vAENMAc3R4FHHv0hiAviD%2BQA&tokens=false

classUint8Array<T>{// ...}leta:Uint8Array<ArrayBufferLike>=newUint8Array();export{}

You'll want to use the scope manager to see whether the identifier is referencing something declared or imported in the file vs. a global. Searching oncontext.sourceCode.getScope should get you some good starting points.

Threading#10477 (comment):

Should I add TypedArray to the default option?

It looks like we don't have consensus on this yet?

• 👍 vote:Bug: [consistent-generic-constructors] improper fix intonew Uint8Array<ArrayBufferLike>() #10445 (comment).
• 👎 vote:fix(eslint-plugin): [consistent-generic-constructors] ignore when constructor is typed array #10477 (comment)

One concern with having default values in the default list is that it gets inconvenient to add to the list rather than replace it. If the default type includes, say,Proxy and all theUint*Arrays, then that's a lot of manual re-typing for folks to write if they want to keep ignoring them.

We're previously had options likeban-types >extendDefaults to get around this, but they're kind of clunky.

@Josh-Cena I think what's confusing me here is:

• What benefit is there to reporting onUint8Array and similar? I.e.: in what situations would one want the rule to report on them?
• If there are none, why not hardcode the rule to always ignore them?

cc@kirkwaiblinger

• What benefit is there to reporting onUint8Array and similar? I.e.: in what situations would one want the rule to report on them?

There's none; I would expect them to be ignored by default.

If there are none, why not hardcode the rule to always ignore them?

Therule should be generic. Any library-specific logic (even those related to native objects) should be injected via options. Built-in objects should not be distinguishable from user-defined objects.

Ok great I think we're aligned? Just confirming, I'm of the opinion that:

• The rule should not report those things by default
• The list should be empty ([]) by default

...so the rule should not provide a way to now report on those built-ins?

IMO if we do go with a list then we'd want to useTypeOrValueSpecifier. Otherwise it'll have the same issue as#10477 (comment) with coincidentally matching names.

But, I'm not sure this is the right step. I started a thread later in this file about it.