ragnarol/awesome-typescript-problem-matcher

A Visual Studio Code Extension for a Webpack's Awesome Typescript Problem Matcher

awesome-typescript-problem-matcher's Issues

Rename awesomets-lint

I don't know what I was thinking when adding that hyphen.

Rename it to "awesometslint"

Merger errors with Language Service

When opening a file that has created a problem from the new problem matcher the error appears twice as the Typescript language service adds its own.

This can be fixed by adding the right owner to the problem matcher. Right now is "webpack" should be "typescript"

"owner": "typescript"

tasks.json version 2.0 causes problem matchers to not work

I tried upgrading to version 2.0 of the tasks.json and I'm running into all kinds of issues where there says there is always a problem with webpack when there are no issues. I had to revert back to 0.1.0 but I still have to press f5 twice to debug because the problem matcher has issues detecting the webpack complete messages (v3.9.1). Is anyone else experiencing this?

Support for tslint-loader

Check that tslint problem matcher works with Webpack and expand $awesometsc to include it if not.

update readme example to latest vscode tasks version

it's a little bit outdated :)