Vscode-eslint: Infer `eslint.validate` from plugins configuration.

[clock157]

demo repo:
https://github.com/clock157/bug-vscode-eslint-typescript

run command can found error but not report in vscode.

set setting.json not work too.

+"eslint.options": {
+        "extensions": [".ts", ".tsx"]
+},

[Sujimoshi]

The same. My config:

{
    "eslint.autoFixOnSave": true,
    "eslint.validate": [ 
        "javascript", 
        "javascriptreact", 
        { "language": "typescript", "autoFix": true },
        { "language": "typescriptreact", "autoFix": true } 
    ],
    "eslint.options": {
        "extensinons": [".ts", ".js", ".tsx", ".jsx"]
    },
}

[dbaeumer]

Strange. This works for me using the repository from https://github.com/Microsoft/vscode-eslint/issues/642#issue-417763561 and adding the following setting.

{
    "eslint.validate": [
        "javascript",
        "javascriptreact",
        { "language": "typescript", "autoFix": true }
    ]
}

[dbaeumer]

Any additional information how to reproduce what you are seeing.

[Sujimoshi]

vscode verison: 1.30.2 (1.30.2)

Eslint extension info:

Name: ESLint
Id: dbaeumer.vscode-eslint
Description: Integrates ESLint JavaScript into VS Code.
Version: 1.8.1
Publisher: Dirk Baeumer
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint

.eslintrc

{
    "parser": "@typescript-eslint/parser",
    "plugins": ["@typescript-eslint"],
    "rules": {
        "@typescript-eslint/no-unused-vars": "error"
    }
}

[Sujimoshi]

Work!!! After update to latest vscode

[dbaeumer]

@Sujimoshi this was a problem on my end not treating versions correctly. I fixed this and releases 1.8.2 which now prereqs the right VS Code version. Sorry for that.

@clock157 any additional information. Are you still seeing this ?

[clock157]

hi @dbaeumer, thanks for your help, It works.

+"eslint.validate": [
+    { "language": "typescript" }
+]

can you set this option to default that tslint will deprecated?

[dbaeumer]

The problem here is that eslint (the npm module) out of the box only validates JS files. Everything else comes in as a configuration. What I can look into is whether I am able to infer this from the plugins section.

[LeoEatle]

Any progress? I still need to config eslint.validate to make typescript eslint work. But in the doc

Improved TypeScript detection - As soon as TypeScript is correctly configured inside ESLint, you no longer need additional configuration through VS Code's eslint.validate setting. The same is true for HTML and Vue.js files.

[dbaeumer]

Actually that got fix for 2.x version of ESLint. TypeScript should work out of the box without providing an eslint.validate setting.

@LeoEatle does the validation happen correctly when you use eslint in the terminal. If this is the case can you please provide me with a GitHub repository I can clone that demos what you are experiencing.