Skip to content
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

[Tracking Issue] ESLint, JSCS Deprecation, and Tests #281

Closed
2 tasks done
nhubbard opened this issue May 2, 2016 · 2 comments
Closed
2 tasks done

[Tracking Issue] ESLint, JSCS Deprecation, and Tests #281

nhubbard opened this issue May 2, 2016 · 2 comments

Comments

@nhubbard
Copy link
Contributor

nhubbard commented May 2, 2016

If any of you follow the JSCS project that we use for coding style, they have deprecated the project in favor of merging with ESLint. I have been reading up on ESLint, and found that I have been doing it wrong all along! 😨

So, this is a tracking issue. We make a checkmark list to show what progress is happening here.

  • Remove JSCS and replace it with ESLint.
  • Add Travis tests to enforce ESLint, StyleLint, and HTML Validator rules.

I expect this entire system to be done by the end of the beta.

@MichMich
Copy link
Collaborator

MichMich commented May 2, 2016

Add travis test on ESLint would make any contribution much more difficult. Maybe we should force this?

@MichMich
Copy link
Collaborator

MichMich commented May 3, 2016

Scratch that. I ran into some issues cased by a PR that wasn't JS linted. FORCE IT! 😈

MichMich added a commit that referenced this issue May 4, 2016
Close #281: ESLint and using the force, Luke
@nhubbard nhubbard closed this as completed May 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants