Sebastián Altamirano

If `exactOptionalPropertyTypes` is set to `false` at https://stackblitz.com/edit/stackblitz-starters-rh2kntpu?file=eslint.config.mjs,tsconfig.config.json&view=editor, there are still type errors. These are for a different issue, but I’m unsure whether they fall under ESLint’s responsibility, the plugins'...

Makes sense! Since `@eslint/markdown` does not add a type anotation for the `plugin` constant, TypeScript does its best to infer one, resulting in that unusual type with `undefined` values. Given...

The helper function is not needed: ```js const processorPluginConfig = { name: "markdown/recommended/plugin", plugins: (processorPlugins = {}), }; const processorProcessorConfig = { name: "markdown/recommended/processor", files: ["**/*.md"], processor: "markdown/markdown", }; const...

What if `exactOptionalPropertyTypes` is added only to `tests/types/tsconfig.json`? This should help detect future incompatibilities. [The tests already use a stricter configuration than the code](https://github.com/eslint/markdown/blob/v6.4.0/tests/types/tsconfig.json#L7).

> ...it should be safe to type each config array with Linter.Config[], if that is the approach we prefer to take. I think using a function, as you suggested, or...