reportUnusedDisableDirectives should probably be a regular rule

[silverwind]

reportUnusedDisableDirectives is currently a config option but I think it would make more sense if it would just be a regular rule which would allow:

• Allow it to be disabled by line (/* eslint-disable-line rule report-unused-disable-directives */)
• Setting it to error level (Allow "reportUnusedDisableDirectives" option to "error" #12703)
• Autofix can be implemented as usual (--report-unused-disable-directives should be autofixable #11815)

Example where it is useful to disable per-line is a imported externally generated file that may or may not be present. import/no-unresolved will warn on it when absent but if I add a per-line disable reportUnusedDisableDirectives will trigger in situations where the file is present. My only option to resolve this is to disable reportUnusedDisableDirectives completely.

(Sorry, for omitting the issue template but none seems to really fit)

[mdjermanovic]

@silverwind thanks for the issue!

This feature needs output (reported problems) from all rules. Any ideas on how could we make reportUnusedDisableDirectives rule with the current architecture?

If it helps with your use case, reportUnusedDisableDirectives is allowed in overrides sections, so it can be set to false for a specific file.

[silverwind]

Thanks for the tip, having reportUnusedDisableDirectives overrideable per-file certainly helps here.

Regarding implementation, I read that it was tried to be implemented as a rule initially but the architecture did not allow it (#9382 (comment)), so it might be impossible currently.

[eslint-deprecated]

Unfortunately, it looks like there wasn't enough interest from the team
or community to implement this change. While we wish we'd be able to
accommodate everyone's requests, we do need to prioritize. We've found
that issues failing to reach accepted status after 21 days tend to
never be accepted, and as such, we close those issues.
This doesn't mean the idea isn't interesting or useful, just that it's
not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.