Add emoji for `type-checked` config about eslint-doc-generator

[ljharb]

type-aware seems like a good name for that.

[JoshuaKGoldberg]

Oh shoot I missed this till now - type-aware is a really interesting name. cc @bradzacher, I actually like it more than type-checked for the reasons stated.

The problem is, we just did a set of config renames like recommended-requiring-type-checking to recommended-type-checked (typescript-eslint/typescript-eslint#6019) last year. And then we released flat config support over the last couple of months.

So... as much as I prefer "aware", I'm not sure that it can be more than just a nice terminology alias for a while in typescript-eslint itself 😞. Which makes it hard to recommend other configs use it.

[ljharb]

I’m confused; what does “type-checked” indicate?

[bmish]

It's just one possible name that plugins might use for configs containing type-aware rules, which would usually have meta.docs.requiresTypeChecking enabled. Discussion in eslint-community/eslint-plugin-eslint-plugin#445.

Note that plugins don't need to use this name or config, as the idea is just to provide emojis for a variety of common or possible config names.

[ljharb]

that seems like a really weird name since it appears to describe the config itself rather than the code it’s linting - nobody should care if the plugin code is type-checked or not.

[bmish]

Hmm perhaps the name is misleading since it's not that the lint rule itself is type-checked but rather that the lint rule takes into account type information while operating on the user's code, so it does have a user-facing impact. Type-checked aka type-aware rules can be smarter as a result.

Either way, I'm not really making a judgment here about whether this is an advisable config name to use, but the name is inspired from typescript-eslint which has been using this convention of type-checked in some of its config names: https://typescript-eslint.io/users/configs#recommended-configurations (CC: @JoshuaKGoldberg)

[bmish]

type-aware sounds nice and concise. I'll defer to @JoshuaKGoldberg on the official typescript-eslint conventions or recommendations but will aim to support any variation here.