Using both ESLint and JSHint

[feimosi]

Is it a good idea to keep both: ESLint and JSHint in the project? It'll print many duplicate linting errors to the console. Also ESLint haven't been attached to the gulp watchers. And lastly, as an enhancement, there's a great eslint-plugin-angular for linting Angular apps.
Referencing #990

[lirantal]

@feimosi do you want to submit a PR to clean it up and add the angular eslint plugin?

[feimosi]

@lirantal sure, no problem. Should get rid of JSHint completely?

[lirantal]

If jshint is redundant then yes obviously remove it in favor of eslint.

[codydaig]

👍

[ilanbiala]

I think the specific duplicates are just some rules we have in both places. I'm not sure if JSHint is has all the features JSHint has and more though, so that will need to be checked if we want to remove JSHint.

[feimosi]

That's the point, ESLint offers the same functionality and even more, so there's no point in using two linting tools. AFAIK it's closely compatible with JSHint, so most of the rules should be there. We just need to do the migration from .jshintrc to .eslintrc. Preferably also add new rules, including code style, but that may need an additional discussion.
Also I think it wouldn't be a bad idea to use the 'extending config' feature from ESLint and use someone else's config as the base e.g. well-known Airbnb rules.
What do you say?

[ilanbiala]

@feimosi If it doesn't throw errors, that sounds good to me. Otherwise, we'll need to just discuss any changes extending an existing config.

[lirantal]

@feimosi we're waiting on that PR from you... :-)