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

Eslint as linter and formatter #430

Merged
merged 17 commits into from Feb 23, 2017

Conversation

Projects
3 participants
@MaciejBaj
Member

MaciejBaj commented Feb 9, 2017

No description provided.

MaciejBaj added some commits Jan 18, 2017

replace jshint with eslint as linter for demanded syntax support
Main reason is the file formatter integration for files format consistency and support for demanded function spacing.

Signed-off-by: Maciej Baj <macie.baj@gmail.com>
files formatted after eslint fix
Signed-off-by: Maciej Baj <macie.baj@gmail.com>

@karmacoma karmacoma added the standards label Feb 10, 2017

@karmacoma karmacoma self-assigned this Feb 10, 2017

karmacoma added some commits Feb 23, 2017

karmacoma added some commits Feb 23, 2017

@karmacoma karmacoma added this to Pending Review in Version 0.7.0 Feb 23, 2017

@coveralls

This comment has been minimized.

Show comment
Hide comment
@coveralls

coveralls Feb 23, 2017

Coverage Status

Coverage increased (+0.005%) to 65.095% when pulling 18ef355 on MaciejBaj:eslint-formatting into a539295 on LiskHQ:development.

coveralls commented Feb 23, 2017

Coverage Status

Coverage increased (+0.005%) to 65.095% when pulling 18ef355 on MaciejBaj:eslint-formatting into a539295 on LiskHQ:development.

@karmacoma karmacoma merged commit 7773f10 into LiskHQ:development Feb 23, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage increased (+0.005%) to 65.095%
Details

@karmacoma karmacoma deleted the MaciejBaj:eslint-formatting branch Feb 23, 2017

@karmacoma karmacoma moved this from Pending Review to Done in Version 0.7.0 Feb 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment