Migration to ESLint

[chaosmonster]

🚀 Feature request

Migrate new projects to ESLint. This is a long-term goal.

Command (mark with an x)

- [x] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [x] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Description

Palantir decided to drop the further development of TSLint (read here).
So a long-term goal for the CLI should be to also migrate the newly created Angular Projects to ESLint. I opened an issue in the codelyzer project to think about migration as codelyzer is coupled to the CLI builds as well

Describe the solution you'd like

Newly created projects should use ESlint

[alan-agius4]

Hi, agreed however this is blocked, since at the moment ESLint is not yet feature complete.

[chaosmonster]

True. Should I link the necessary issues of TSLint and ESLint as well?

[alan-agius4]

That wouldn't hurt, though when eslint will be feature complete, tslint will be deprecated, so it's safe to assume that when this gets deprecated we should be in a point that we can migrate.

[JamesHenry]

I’m coordinating this with @alexeagle, stay tuned

[destus90]

TSLint has been deprecated palantir/tslint#3865 (comment).

[IGassmann]

@JamesHenry will the ESLint configuration be aligned with the Google JavaScript Style Guide, or any other style guide?