Open Samuel-Therrien-Beslogic opened 3 months ago
Ideally this would be handled at the ESLint level rather than within any specific rule. That's a bigger task though and not one that excludes this.
Ideally this would be handled at the ESLint level rather than within any specific rule.
Agreed.
As a note for anyone else reading this, ESLint has https://eslint.org/docs/v8.x/use/configure/rules#report-unused-eslint-disable-comments , but that has a few issues that don't obsolete @eslint-community/eslint-comments/no-unused-disable
:
@eslint-community/eslint-comments/no-unused-disable
at the moment, but that's what this request is about.I meant that the option to disable autofix for any individual rule should be supported by ESLint, as eg. Biome does: https://biomejs.dev/linter/#configure-the-rule-fix :)
Ah yes, that too !
Normally to disable a rule's autofix through configuration, I'd simply use https://github.com/aladdin-add/eslint-plugin/tree/master/packages/no-autofix . But due to the special way this rule works (as mentionned in its documentation https://eslint-community.github.io/eslint-plugin-eslint-comments/rules/no-unused-disable.html#known-limitations ),
no-autofix/@eslint-community/eslint-comments/no-unused-disable
doesn't work.I want to be warned about rules that no longer trigger, but I don't want that change to be automated.