GitHub user felizbear opened a pull request:
https://github.com/apache/zeppelin/pull/1818
[ZEPPELIN-1873] Use exclusively eslint for javascript code linting
### What is this PR for?
[jscs](http://jscs.info) has merged with [eslint](http://eslint.org),
therefore both should be unified as eslint and jscs should be removed
### What type of PR is it?
Improvement
### Todos
* [x] - Move jscs config to eslint
* [x] - Remove jscs
* [x] - Upgrade eslint
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1873
### How should this be tested?
Build and dev modes should lint as expected
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/felizbear/zeppelin devops-eslint
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1818.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1818
----
commit 3a35792831255e994a7831af2d10eb416927549d
Author: felizbear <i...@nflabs.com>
Date: 2016-12-29T09:21:14Z
move jscs rules over to eslint
commit e0e0ba2906b4150a6e2f4e8ff4b7e2aee29fb8f0
Author: felizbear <i...@nflabs.com>
Date: 2016-12-29T09:22:01Z
remove jscs
commit 753bf4f5ed8539adff9cae16732be35965b1541e
Author: felizbear <i...@nflabs.com>
Date: 2016-12-29T09:35:18Z
update eslint version
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
