Persistent syntax errors in non PS files

[jhoneill]

System Details

### VSCode version: 1.43.1 fe22a9645b44368865c0ba92e2fb881ff1afce94 x64

### VSCode extensions:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]


### PSES version: 2.1.0.0

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      7.0.0
PSEdition                      Core
GitCommitId                    7.0.0
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Issue Description

When the default file type is PowerShell, and something else (e.g. JSON) is pasted into a new Window many syntax errors are detected and shown in the problem window

However if the document type changed to JSON or Plain Text the errors are not removed

Even if the file is closed the errors remain

Expected Behaviour

PowerShell syntax errors should only appear while the file is present and believed to be a PowerShell file.

[TylerLeonhardt]

If you made a single file edit, do the Problems go away? Like, add a single space in the file.

[jhoneill]

no, sadly

[TylerLeonhardt]

If you add another syntax error (like a random extra } or something) do you get additional Problems showing up?

[jhoneill]

No, once the type is changed to plain text, the errors are frozen. No new ones get added , but the old ones remain.

[TylerLeonhardt]

It seems like other extensions have this issue as well... I just reproed with the C# extension:

Plain text file, C# warning:

@jhoneill since I'm also seeing this with C# it's going to be an issue on VS Code itself:
https://github.com/Microsoft/vscode

Can you open an issue there?

[jhoneill]

microsoft/vscode#93271 basic said it's the responsibility of the extensions...

[TylerLeonhardt]

PR out for this.