eslint-plugin-eslint-comments
eslint-plugin-eslint-comments copied to clipboard
Additional ESLint rules for directive comments of ESLint.
This rule enforces `eslint-disable-line` and `eslint-disable-next-line` comments to be line comments instead of block comments.
It can be unclear to people why a rule should not be disabled. The only way to know is to look for a comment in the ESLint config where the...
the rule actually works correctly, and in vscode it is not highlighted, but in termital eslint shows an error `"total-functions/no-unsafe-type-assertion' rule is disabled but never reported"` linked issue: https://github.com/danielnixon/eslint-plugin-total-functions/issues/38#issuecomment-664050009
consider the following example: ```ts /*eslint eslint-comments/disable-enable-pair: error */ /*eslint eslint-comments/require-description: error */ /*eslint-disable no-undef, no-unused-vars -- My reason for doing this is XYZ */ var foo = bar() /*eslint-enable...
When enabling the `no-restricted-disable` rule, I guess both the following statements should be reported as errors: ```js /* eslint-disable max-lines */ /* eslint max-lines: off */ ``` But only the...
Hi, I was following the examples for https://mysticatea.github.io/eslint-plugin-eslint-comments/rules/no-restricted-disable.html and noticed that the underlying `ignore` package handles un-ignores after `'*'` strangely. When you lock down disabling of all rules with `'*'`,...
From [the docs for no-restricted-disable](https://github.com/mysticatea/eslint-plugin-eslint-comments/blob/b35ad0bfbff88440ec8506bfc77e3f6599820816/docs/rules/no-restricted-disable.md), it doesn't look like it's possible to do something like this: ``` { "eslint-comments/no-restricted-disable": ["warn", { "level": "error" }] } ``` This would allow disabling...
Adding a test to verify if this rule is working for capitalized-comments. I could not replicate the issue locally on linux where earlier in the week I could on windows....
This issue was opened (I think incorrectly) in eslint/eslint#12548 but it seems the problem comes from this plugin. I would be willing to try replicate a test for this and...
**Tell us about your environment** Wrongly assigned this to eslint first (https://github.com/eslint/eslint/issues/12125) * **ESLint Version: 6.1.0** * **Node Version: v11.13.0** * **npm Version: 6.7.0** **What parser (default, Babel-ESLint, etc.) are...