-
-
Notifications
You must be signed in to change notification settings - Fork 638
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
Add eslint-plugin-eslint-plugin
#818
Conversation
There’s no need to make eslintrc valid json; trailing commas and comments are a good feature. |
I agree those are good features. It's just a bit inconvenient to use those in JSON files since some IDEs will show syntax warnings. It's also confusing that the That's why I normally use the JS format of the config file Anyways, I reverted the changes to the original lines in |
c2ae0f3
to
efc2aaf
Compare
Codecov Report
@@ Coverage Diff @@
## master #818 +/- ##
=======================================
Coverage 99.22% 99.22%
=======================================
Files 98 98
Lines 1417 1417
Branches 477 477
=======================================
Hits 1406 1406
Misses 11 11 Continue to review full report at Codecov.
|
3c711de
to
813b58e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
94a4684
to
f1414cf
Compare
recommended
practices for eslint rules and rule tests using eslint-plugin-eslint-plugin which is commonly used internally by eslint plugins.Exports rules usingexport default
instead ofmodule.exports =
. Why?This is needed so thateslint-plugin-eslint-plugin
will recognize the rules sinceexport default
is expected in files that usesourceType: module
.For module files (whichimport
statements instead ofrequire
), we might as well useexport
statements instead ofmodule.exports
too to adopt fully modern syntax.