Steps to Reproduce:
Issue also noticed here:
https://github.com/angelozerr/tslint-language-service/issues/76
This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.
Happy Coding!
@mjbvz Hi, please revisit this issue. tslint-language-service is not an extension but a plugin of typescript.
Hey @Tyriar @mjbvz, not sure what your rationale was for closing, but I think it's likely that this is a VSCode bug, not a bug in tslint-language-service. The plugin is completely broken (no errors show up at all) when used in VSCode 1.25.1, and it works fine (all errors show up) in VSCode 1.24.1 as well as the latest versions of WebStorm and Sublime.
My guess is that VSCode changed its mechanism for reporting TypeScript errors from the TS language service, and is mistakenly no longer reporting any errors provided by language service extensions.
Most helpful comment
Hey @Tyriar @mjbvz, not sure what your rationale was for closing, but I think it's likely that this is a VSCode bug, not a bug in tslint-language-service. The plugin is completely broken (no errors show up at all) when used in VSCode 1.25.1, and it works fine (all errors show up) in VSCode 1.24.1 as well as the latest versions of WebStorm and Sublime.
My guess is that VSCode changed its mechanism for reporting TypeScript errors from the TS language service, and is mistakenly no longer reporting any errors provided by language service extensions.