Skip to content
This repository has been archived by the owner on Aug 29, 2019. It is now read-only.

Add support for tslint.exclude #8

Open
Torhal opened this issue May 30, 2018 · 2 comments
Open

Add support for tslint.exclude #8

Torhal opened this issue May 30, 2018 · 2 comments

Comments

@Torhal
Copy link

Torhal commented May 30, 2018

Currently, this setting only seems to be available in the other plugin. VSCode was complaining that it was an unknown setting until I disabled the TSLint (vnext) plugin and enabled the "regular" TSLint plugin, after which the files/directories I'd specified were, indeed, ignored. Losing the more advanced linting options isn't a worthwhile tradeoff for me, though.

@egamma
Copy link
Member

egamma commented May 30, 2018

This is unfortunately correct there are some feature gaps between vscode-tslint and this extension which is based on the TypeScript server plugin provided by the tslint-language-service module (which is a fork of the vscode-tslint extension)… Something that needs to be reconciled in the near future.

Just curious since when are you using the TSLint (vnext) extension? I´ve published a new version yesterday, did the older version work for you?

@Torhal
Copy link
Author

Torhal commented May 30, 2018

I've been using it for roughly a year, but only within the past few days have I looked into trying to exclude specific files/directories from linting due to some generated DB migrations I'd rather not have to edit to make VSCode stop complaining. The node_modules linting has always been an aggravation, but since it isn't my own code and I only jump in to look at definitions from time to time, it wasn't critical.

I understand the feature gaps, and prefer the power of vnext, so I'll just deal with it for now.

Thanks!

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

2 participants