no-unused-disable does not work when turned on in a flat config

[Zamiell]

n/t

[FloBam]

Just to add my use case here since I've seen the discussion in #133

It's possible to configure the severity globally with

export default [
    linterOptions: {
      reportUnusedDisableDirectives: 'off',
    },
    [...]
];

With a rule it would be possible to add a file matcher and apply it accordingly (what I would prefer).

Concrete use case: We generate api code via openapi generator, which includes the comments

/* tslint:disable */
/* eslint-disable */

I would like to exclude the directory of the generated code, but everything else should be marked depending of the configured severity(for example error).

[Samuel-Therrien-Beslogic]

#249 (comment)

Idk if that still true, but in #234 (comment) I mentioned that the ESLint option "Doesn't seem to be picked up by extending configurations". But even if it is now:

There's one use-case where it's still not fully redundant: Flagging without autofixes. Which is especially sensical with this rules as you may not want a "disable removal" to slip through unnoticed due to a bad configuration change.

• @eslint-community/eslint-comments/no-unused-disable option to disable autofix #234

Using the npmjs.com/package/eslint-plugin-no-autofix plugin:

'@eslint-community/eslint-comments/no-unused-disable': 'off',
'no-autofix/@eslint-community/eslint-comments/no-unused-disable': 'error',
In VSCode settings:

"eslint.codeActionsOnSave.rules": [
// Clearing imports, unused vars and comments because of commented code while testing is annoying
...
"!@eslint-community/eslint-comments/no-unused-disable",
"*"
],
There is a RFC to obsolete eslint-plugin-no-autofix and include the functionality in base ESLint, but I need help completing that

• Change Request: Ability to disable autofixes on a per-rule basis eslint/eslint#18696
• eslint/rfcs#125 (files)

The RFC currently doesn't even mention linterOptions.reportUnusedDisableDirectives as I just learned about it. I'll have to add it.

However, this rule is currently broken on flat-configs anyway, unfortunately

• no-unused-disable does not work when turned on in a flat config #244