We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Tests microsoft/vscode-eslint#802
Complexity: 3
The ESLint extension now has better support for TypeScript. Test that this is working as expected if a workspace is setup correctly for eslint usage.
Install the latest version of the ESLint extension from here: https://github.com/microsoft/vscode-eslint/releases/tag/2.0.1-next.1
"@typescript-eslint/parser
"parser": "@typescript-eslint/parser", "parserOptions": { "ecmaVersion": 6, "sourceType": "module" }
A blueprint repository can be found here: https://github.com/microsoft/vscode-eslint/tree/2.0.1-next.1/playgrounds/ts
Ensure the following:
Please report issues here: https://github.com/microsoft/vscode-eslint/issues
The text was updated successfully, but these errors were encountered:
Works nicely. I also set it up for our VS Code repo. I tested on macOS.
Sorry, something went wrong.
No branches or pull requests
Tests microsoft/vscode-eslint#802
Complexity: 3
The ESLint extension now has better support for TypeScript. Test that this is working as expected if a workspace is setup correctly for eslint usage.
Prerequisite
Install the latest version of the ESLint extension from here: https://github.com/microsoft/vscode-eslint/releases/tag/2.0.1-next.1
Setup
"@typescript-eslint/parser
A blueprint repository can be found here: https://github.com/microsoft/vscode-eslint/tree/2.0.1-next.1/playgrounds/ts
Ensure the following:
Please report issues here: https://github.com/microsoft/vscode-eslint/issues
The text was updated successfully, but these errors were encountered: