Please add tslint-language-service to dependencies

[angelozerr]

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request

Versions.

Repro steps.

The log given by the failure.

Desired functionality.

Mention any other details that might be useful.

Like #5497 please add TSLint Language Service plugin.

And give an option to declare it in the tsconfig.json like this:

{
  "compilerOptions": {
    "plugins": [
      { "name": "tslint-language-service"}
    ]
  }
}

This TypeScript plugin can be used with any IDE (VSCode, WebStorm, Eclipse, etc) to provide tslint diagnostic and codefix in your editor.

Thanks!

[filipesilva]

Oh sorry, this wasn't fixed by #6144.

[filipesilva]

I'm marking this as a discussion though, adding it depends on up to date versions of a lot of things so it's not a cut and dry thing.

[ValeryVS]

As far as I know, it depends on typescript@2.3. And @angular/cli@1.1.x also depends on this typescript version.

I installed package, add lines in tsconfig and disable tslint extension in my vscode.
All seems to be working properly.

[ValeryVS]

With tslint-language-service it is possible to view errors for rules, that require type checking.
But not all...
For example, I can't see no-unused-variable errors in VSCode.

Rules, that require type checking, aren't work with current vscode-tslint plugin any way.

[angelozerr]

@ValeryVS the goal of this issue is to integrate tslint-language-service with angular-cli.

For example, I can't see no-unused-variable errors in VSCode.

Yes it's a known problem, you can read it at https://github.com/angelozerr/tslint-language-service (in Notice section)

If you have problems with tslint-language-service, please create issues at https://github.com/angelozerr/tslint-language-service/issues

[mgechev]

For now tslint without the language service has been sufficient for the CLI. Let's close this feature request for now and revisit in future.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}