Skip to content
This repository has been archived by the owner on Aug 4, 2020. It is now read-only.

Refactor rules to use eslint-rule-composer #138

Merged
merged 1 commit into from
Mar 30, 2018
Merged

Conversation

existentialism
Copy link
Member

@existentialism existentialism commented Mar 28, 2018

Closes #135.
Closes #127.
Closes #137. (Sorry for the delay, and thanks for the PR @VictorHom!)

/cc: @kaicataldo @kentcdodds @not-an-aardvark

Copy link
Member

@hzoo hzoo left a 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

@existentialism
Copy link
Member Author

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.

Copy link
Member

@kaicataldo kaicataldo left a 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.
Copy link
Member

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants