-
Notifications
You must be signed in to change notification settings - Fork 335
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
[Bug] No linting for .ts
and .tsx
files when using vue-eslint-parser
#1266
Comments
This is actually by design since I didn't want to break existing users. You should simply remove the setting since it is not necessary for your setup anymore. Let me know if everything works as expected when the setting is removed. |
@dbaeumer Please pardon me if I'm wrong, I think you misunderstood the issue. My previous config {
"eslint.validate": [
"javascript",
"javascriptreact",
"typescript",
"typescriptreact"
]
} You can try my repro with the default |
Any additional steps? |
@dbaeumer No, there's none. It's quite strange, I'm using the following as a workaround now, no problems so far: {
"eslint.validate": [
"javascript",
"javascriptreact",
"typescript",
"typescriptreact"
]
} |
That is really strange since it works for me without the |
@wenfangdu are you using windows by any chance? if so, can you try the same repo in another windows computer along with linux/osx? My findings are that it fails without that validate options if you use windows, whereas in linux/OSX, it works out of the box. |
@baranelitez Yes, I'm using Windows 10. @dbaeumer I think this might be the reason? |
@dbaeumer Sorry to bother 🙏, is it released? It's still reproducible for me. |
Only has a new insider here: https://github.com/microsoft/vscode-eslint/releases/tag/release%2F2.1.24-Insider If you want to give it a try you can download the VSIX and install using the |
Quote from README.md:
Therefore, my config:
{ "eslint.validate": [] }
Repro: https://github.com/wenfangdu/vue-eslint-parser-repro
Seems when using
vue-eslint-parser
,.ts
and.tsx
files aren't auto-detected unless I explicitly specify:The text was updated successfully, but these errors were encountered: