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

Migrate from jshint to eslint #472

Merged
merged 8 commits into from
Oct 28, 2015
Merged

Migrate from jshint to eslint #472

merged 8 commits into from
Oct 28, 2015

Conversation

tmcgee
Copy link
Member

@tmcgee tmcgee commented Oct 26, 2015

No description provided.

modified JS files so they pass extensive eslint tests
updated package.json and Gruntfile.js for hinting locally
    using `grunt hint` and on build with travis-ci for each commit.
The travis run should fail if there are eslint errors.
using new container-based infrastructure.
eslint-stylish is now included with eslint so should not be required.
travis build failed as expected with errors listed in build job log.
@btfou
Copy link
Contributor

btfou commented Oct 28, 2015

@tmcgee This has issues and is unmergeable.

@tmcgee
Copy link
Member Author

tmcgee commented Oct 28, 2015

Hmmm. There were no conflicts when submitted. It most likely the 2 files with proj4 changes that were just merged. I will review later tonight.

@btfou
Copy link
Contributor

btfou commented Oct 28, 2015

Just a heads up :)

@tmcgee
Copy link
Member Author

tmcgee commented Oct 28, 2015

@btfou: good to go now.

btfou added a commit that referenced this pull request Oct 28, 2015
@btfou btfou merged commit 711693a into develop Oct 28, 2015
@btfou
Copy link
Contributor

btfou commented Oct 28, 2015

Good work. Looking forward to pulling this in.

@tmcgee tmcgee deleted the cleanup/migrate-to-eslint branch October 29, 2015 22:20
@tmcgee tmcgee added this to the v1.4.0 milestone Nov 23, 2015
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.

2 participants