Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Ashokaditya <am.struktr@gmail.com>
This commit is contained in:
parent
272a2af379
commit
693eb72e0c
1 changed files with 8 additions and 4 deletions
|
@ -47,17 +47,21 @@ file types.
|
|||
"eslint.validate": [
|
||||
"javascript",
|
||||
"javascriptreact",
|
||||
{ "language": "typescript", "autoFix": true },
|
||||
{ "language": "typescriptreact", "autoFix": true }
|
||||
"typescript",
|
||||
"typescriptreact",
|
||||
]
|
||||
----
|
||||
|
||||
Although, starting with https://github.com/microsoft/vscode-eslint#version-204[ESLint v2.0.4], there is no need to use `eslint.validate` to parse typescript files as it works out of the box.
|
||||
|
||||
`eslint` can automatically fix trivial lint errors when you save a
|
||||
file by adding this line in your setting.
|
||||
|
||||
[source,json]
|
||||
----
|
||||
"eslint.autoFixOnSave": true,
|
||||
"editor.codeActionsOnSave": {
|
||||
"source.fixAll.eslint": true
|
||||
}
|
||||
----
|
||||
|
||||
:warning: It is *not* recommended to use the
|
||||
|
@ -67,4 +71,4 @@ the multiple `.eslintrc.js` files across the project and some of them
|
|||
use the https://www.npmjs.com/package/prettier[NPM version of Prettier].
|
||||
Using the IDE extension might cause conflicts, applying the formatting
|
||||
to too many files that shouldn’t be prettier-ized and/or highlighting
|
||||
errors that are actually OK.
|
||||
errors that are actually OK.
|
||||
|
|
Loading…
Reference in a new issue