Closed KostyaTretyak closed 5 years ago
Seems to be working for me:
What VS Code version and OS are you on?
VS Code 1.33.1, Ubuntu 16.04 (OS: Linux x64 4.15.0-48-generic)
Maybe you did not do git checkout 11a929
before?
I'm on that commit. Are the implicitAny errors and other non-tslint errors expected?
You can also check the TS Server log:
"typescript.tsserver.log": "verbose",
TypeScript: Open TS Server log
commandtsserver.log
file in itLook through that log file for lines that mention tslint, such as Info 224 [10:46:52.902] [typescript-tslint-plugin] "Computing tslint semantic diagnostics for '/Users/matb/projects/san/router/src/node.ts'"
If you can share the log, I can see if it shows something odd going on
My log file: tsserver.log
In tsconfig.json
: "compilerOptions": { "noImplicitAny": true }
It looks like something going wrong with your copy of typescript, see the line:
Err 104 [21:11:10.146] Exception on executing command delayed processing of request 17:
Debug Failure. False expression.
Error: Debug Failure. False expression.
at Object.first (/usr/share/code/resources/app/extensions/node_modules/typescript/lib/tsserver.js:1097:15)
at getArgumentArityError (/usr/share/code/resources/app/extensions/node_modules/typescript/lib/tsserver.js:50167:32)
at resolveCall (/usr/share/code/resources/app/extensions/node_modules/typescript/lib/tsserver.js:50307:41)
at resolveCallExpression (/usr/share/code/resources/app/extensions/node_modules/typescript/lib/tsserver.js:50593:20)
at resolveSignature
...
If you disable this extension, do you get any errors in this project?
Also, can you please test this using typescript@next
by following these instructions. https://github.com/Microsoft/TypeScript/issues/30591 suggest this debug failure should be fixed in @next
With typescript@3.4.5
the problem has disappeared. @mjbvz, thanks for the help!
If you do the following:
you can see the tslint errors:
then open
src/router.ts
in VS Code and you can see that thevscode-typescript-tslint-plugin
not work.I think the bug is related to the spread operator. If we comment out 37 line, the plugin works as expected: