-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
TSLint bombs on .vue files for some rules from tslint-microsoft-contrib #2712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The failing rules are These are bugs that should be fixed in TSLint. We should note that |
Hm, it seems the tslint-microsoft-contrib recommended ruleset enables them which is what threw me off? As in, the sequence of events for me was: using the TSLint ruleset was fine, adding the contrib one caused the bug to manifest, it didn't occur to me to look into which project has the actual rules complaining. Anyway, thanks for taking a look at this @JoshuaKGoldberg, should I refile this with TSLint? Additionally, maybe tslint-microsoft-contrib shouldn't enable |
Yes please 😊. I'm already planning on taking a look anyway, but it'd be nice for tracking there.
Agreed! |
@JoshuaKGoldberg - Done at palantir/tslint#4273, thanks. |
@LinusBorg, @JoshuaKGoldberg - in light of the investigation leading to other culprits, maybe this issue can be closed as superseded by those other issues? |
Version
3.0.5
Reproduction link
https://github.com/millimoose/vue-tslint-microsoft-contrib-bug
Node and OS info
Node v10.11.0, npm 6.4.1, Typescript 3.1.2, TSLint 5.11.0, Ubuntu 18.04.1 LTS on WSL on Windows 10
Steps to reproduce
Run
npm run lint --no-fix
What is expected?
The lint runs without errors
What is actually happening?
I get the following stack trace:
The text was updated successfully, but these errors were encountered: