-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable comments/require-description
rule
#26
Comments
Thanks for this @junyper! We already use the plugin itself here: I love the idea of adding this rule, but we'll need to get more feedback before progressing. |
Ok. I edited this to reflect adding just that one rule. |
We still plan to do this, but want to add a codemod for this first. |
comments/require-description
rule
Resolves #26 BREAKING CHANGE: ESLint disable directives (comments) now require a description. When migrating to this version, you may want to disable this rule for some files.
Resolves #26 BREAKING CHANGE: ESLint disable directives (comments) now require a description. When migrating to this version, you may want to disable this rule for some files.
Resolves #26 BREAKING CHANGE: ESLint disable directives (comments) now require a description. When migrating to this version, you may want to disable this rule for some files.
Resolves #26 BREAKING CHANGE: ESLint disable directives (comments) now require a description. When migrating to this version, you may want to disable this rule for some files.
Resolves #26 BREAKING CHANGE: ESLint disable directives (comments) now require a description. When migrating to this version, you may want to disable this rule for some files.
Resolves #26 BREAKING CHANGE: ESLint disable directives (comments) now require a description. When migrating to this version, you may want to disable this rule for some files.
🎉 This PR is included in version 5.0.0 🎉 The release is available on: |
We might want to consider setting the require-description rule to encourage adding a description to explain why an eslint rule has been disabled. That might be best set as a warning vs an error since we will probably have a lot of failures to address.
The text was updated successfully, but these errors were encountered: