Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

How does this relate to the existing tslint plugin from egamma? #7

Closed
chillitom opened this issue Oct 31, 2018 · 2 comments
Closed

Comments

@chillitom
Copy link

Just curious if this is a replacement for or in addition to the existing popular VS Code tslint plugin from @egamma?

@csvn
Copy link

csvn commented Oct 31, 2018

It's meant to be a replacement. By making the linting run as a Typescript plugin, it avoids the issue where TSLint runs an extra Typescript program instance in the same workspace, as well as being able to use certain rules that require type info.

There is a gap in the functionality of this plugin compared to vscode-tslint, that was being tracked in this issue on the original fork of the TS plugin.

The Typescript tslint plugin is being actively worked on, and the repo was published just some days ago, so there might still be some rough edges. Considering the speed that the VSCode team has in building features, I would not be suprised if this was plugin was the most popular and used one in the near future.

@egamma
Copy link
Member

egamma commented Nov 1, 2018

@csvn is correct the goal is to gradually migrate from vscode-tslint to this new extension that uses the typescript plugin. This is a rough roadmap microsoft/typescript-tslint-plugin#1

@egamma egamma closed this as completed Nov 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants