Task: Typescript errors disappear after document closed

[neoncom]

• VSCode Version: 1.22.1 (newest) (typescript 2.8.1)
• OS Version: Windows 10 64bit

I expect typescript errors from all files to show until they have been fixed.

Instead, they disappear as soon as the document is closed again (e.g. by randomly clicking on the error list, which causes documents to open & close again)

Steps to Reproduce:

1. Use this tasks.json (check if the project path fits you first)

{
    "version": "2.0.0",
    "command": "tsc",
    "isShellCommand": true,
    "args": [
        "-w",
        "-p",
        "."
    ],
    "showOutput": "silent",
    "isBackground": true,
    "problemMatcher": {
        "base": "$tsc-watch",
        // "owner": "typescript",
        //  "applyTo": "allDocuments"
    }
}

2. Start the task
3. Errors will show in error list (hopefully, if there are errors at all)
4. Randomly click between errors of different files in error list. The files will open and close automatically (if they are not pinned). When a file closes, it's errors disappear!

What I have tried:

• $tsc-watch matcher without any other options
• owner property "typescript" or something artificial
• applyTo property all possibilities
• in settings: typescript.validate.enable === false

The "best" in my trial and error endevour I have got was that the errors just persisted, even when fixed, lol :)

My user settings (don't have workspace settings)

{
    "terminal.integrated.shell.windows": "C:\\Windows\\System32\\cmd.exe",
    "editor.wordWrap": "on",
    "explorer.confirmDelete": false,
    "editor.quickSuggestions": {
        "other": false,
        "comments": false,
        "strings": false
    },
    "editor.autoClosingBrackets": false,
    "explorer.confirmDragAndDrop": false,
    "editor.acceptSuggestionOnCommitCharacter": false,
    "window.zoomLevel": 0,
    "explorer.autoReveal": true,
    "editor.suggestOnTriggerCharacters": true,
    "editor.acceptSuggestionOnEnter": "on",
    "editor.parameterHints": true,
    "typescript.referencesCodeLens.enabled": false,
    // "typescript.validate.enable": false
}

Does this issue occur when all extensions are disabled?: Yes

[dbaeumer]

Matt Bierner (@mjbvz) the reason for this is that the errors from the TS language server and the tsc -w task have the same owner (which they need, otherwise you see errors twice). Now when the file closes the TS extensions removes the errors from the file. I somehow remember that I had special code in that I fetched errors from files that have been through an open / close cycle until the file disappears.

The same problem happens for example without the tsc watch task. Have two ts files open where one depends on the other, have an error and close the one with the error. Observer the error list is empty.

At the end the TS language server should have a project wide compile.

For the tsc -w case I can look into restoring errors when files are closing.

[massimonewsuk]

We recently swapped from Flow to TypeScript.

In our previous workflow with Flow, the errors would remain when we opened/closed files.

However, with Typescript, none of the errors show by default (when all files are closed). For this reason, we use VSCode's Tasks -> Run Build Task, to run the detected tsconfig.watch. This is great because it shows all errors across the project without having to open files.

However, when we open a file then close it, the error disappears from the problems tab (same issue as described above).

We would love for there to be a configuration option to disable removing errors from problems tab until they are fixed. This would be a simple fix. An even cooler one would be for this behaviour to be automatic when using a typescript watcher.

[dbaeumer]

Matt Bierner (@mjbvz) in the past the typescript extension did keep all files that were open and reported errors in a list and rechecked them even if they were closed. This feature seems to got removed. Any reason for this?

[massimonewsuk]

Our team moved from Flow to TypeScript recently and this is one thing they keep bringing up as a downside... Matt Bierner (@mjbvz) any comments on this?

[peterstarling]

this looks like a regression to me, it didn't use to be like that

[dbaeumer]

You can always run the tsc: watchtaks contributed by the TypeScript extension. This will compile the whole project and watch for file changes.

[massimonewsuk]

Yes but after you close a file, the errors disappear from the file browser bar and the IDE's problems summary

[dbaeumer]

Agree. (see my command #47386 (comment))

[mjbvz]

I’m checking in a change to keep the diagnostics around on close, but the problem de-duplication seems incorrect here. Here are the states:

Open workspace with no open files and start watch task

• Should get errors for index.ts from problem matcher

Now open index.ts in vscode

• Still should have errors from problem matcher
• And now we should have errors from TS too.
• These have same owner so only one instance of each problem should be reported by vs code in the problems panel

Close index.ts

• Back to first state
• We should start using the problems matcher errors again
• But currently we go to having zero errors instead