-
Notifications
You must be signed in to change notification settings - Fork 13k
Closed
Labels
BugA bug in TypeScriptA bug in TypeScriptFixedA PR has been merged for this issueA PR has been merged for this issue
Milestone
Description
From @nwehrle on February 9, 2016 21:17
I use eslint to lint my jsx files. Before I switched to salsa, the linting inside the editor worked fine. After switching to salsa the linting fails inside the editor.
Linting from the shell still works without any errors or warnings.
I expect vscode to not show any linting errors.
System:
OSX 10.11.2
vscode 0.10.8
db71ac615ddf9f33b133ff2536f5d33a77d4774e
jsconfig.json:
{
"compilerOptions": {
"target": "ES6",
"module": "system",
"experimentalDecorators": true
},
"exclude": [
"node_modules"
]
}
User settings:
{
"javascript.validate.enable": false,
"editor.tabSize": 2,
"files.trimTrailingWhitespace": true,
// Migrated from previous "File | Auto Save" setting:
"files.autoSave": "onFocusChange"
}
Partial eslintrc:
"rules": {
"func-names": 0,
"no-unused-expressions": 0,
"id-length": 0,
"no-multi-spaces": 0,
"no-mixed-spaces-and-tabs": 2,
"no-unused-vars": [1, {"vars": "all", "args": "none"}],
"react/jsx-uses-react": 1,
"react/prop-types": 0,
"no-console": 0
},
"plugins": [
"react"
]
Copied from original issue: microsoft/vscode#2866
sibelius, wub, vv13, guido4000 and idoo
Metadata
Metadata
Assignees
Labels
BugA bug in TypeScriptA bug in TypeScriptFixedA PR has been merged for this issueA PR has been merged for this issue