-
-
Notifications
You must be signed in to change notification settings - Fork 59
Refactor rules to use eslint-rule-composer #138
Conversation
9301fc1
to
3113581
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.
nice! less copying is great and makes these kinds of one-off changes possible and simple
curious about testing, if copying the tests would be necessary but maybe that's a complexity that we don't need
3113581
to
a7a920e
Compare
Yeah, re: testing, might be nice to have a util (maybe in composer itself?) that allows us to run ESLint tests for a rule so that any mods we make don't cause regressions without needing to include the them manually in this (or other) projects. |
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.
Awesome stuff! Am I excited that we're slowly chipping away at all this cruft around custom parsers 🎉
Would love to find a solution using eslint-rule-composer
for tests.
/** | ||
* @fileoverview Rule to flag use of constructors without capital letters | ||
* @author Nicholas C. Zakas | ||
* @copyright 2014 Jordan Harband. All rights reserved. |
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.
lol, i forgot i modified this rule forever ago
Refactor rules to use eslint-rule-composer
Closes #135.
Closes #127.
Closes #137. (Sorry for the delay, and thanks for the PR @VictorHom!)
/cc: @kaicataldo @kentcdodds @not-an-aardvark