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

style(prettier): Use prettier for code formatting #710

Merged
merged 2 commits into from
Apr 10, 2017
Merged

style(prettier): Use prettier for code formatting #710

merged 2 commits into from
Apr 10, 2017

Conversation

tmcw
Copy link
Member

@tmcw tmcw commented Apr 10, 2017

This commit switches to prettier for our code style.

This saves us style issues. Also adds husky and lint-staged for pre-commit testing

Refs #709

@tmcw tmcw force-pushed the prettier branch 2 times, most recently from 7fdeb6a to fa275be Compare April 10, 2017 18:09
This saves us style issues. Also adds husky and lint-staged for pre-commit testing

Refs #709
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 96.869% when pulling 16f945a on prettier into e2915dc on master.

@tmcw tmcw merged commit 25152ed into master Apr 10, 2017
@tmcw tmcw deleted the prettier branch April 10, 2017 18:25
@arv
Copy link
Contributor

arv commented Apr 14, 2017

It is kind of bad that we lost eslint's feature to detect unused variables. That feature has been a life saver in many projects.

@tmcw
Copy link
Member Author

tmcw commented Apr 14, 2017

Totally, I hear that. We could bring back eslint for static analysis like without using the style-guide parts.

tmcw added a commit that referenced this pull request May 1, 2017
tmcw added a commit that referenced this pull request May 1, 2017
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

Successfully merging this pull request may close these issues.

None yet

3 participants