Parse error reported when viewing output channels

[KamasamaK]

This extension is causing the following errors to appear when viewing their respective channels in the Output pane:

[IronGeek]

I think I'm having the same issue...

When editing a regular JSON file (doesn't have to be a json-tmLanguage file), any invalid entry will add new item to the VS Code Problems pane. These newly added items however stays and does not get removed from the pane although the invalid entry has been fixed.

Here some screen captures to show what I'm talking about.

With the extension enabled:

With the extension disabled:

It seems the extension is validating JSON files using its own JSON validator but fail to do a proper clean-up afterwards. Not sure why the extension needs to do this though, considering VS Code already does the same thing using its own built-in JSON validator?

[jamesharris-garmin]

This happens for any file supported by this plugin. I have seen this occur when editing python files as well.

[tcd]

This is the most annoying bug I've ever seen. I literally had to restart vscode 2 or 3 dozen times yesterday to clear errors caused by this. This is a fantastic plugin, but damn, this bug is literally the worst.

[vthorsteinsson]

I also have this bug, and it is pretty annoying. The tmLanguage extension seems to be attempting to parse everything, regardless of file type or file extension.

[flying-sheep]

Seems like there’s two bugs in here: The fact it parses everything it supports and that it doesn’t clear errors once they’re fixed. The latter is worse.

[vthorsteinsson]

Agree, I have the same bug. Super annoying.

[szTheory]

Deactivating this plugin fixed the error for me.

[ghost]

@KamasamaK I also faced the same issue. There is a vscode extension called TextMate Languages Which is causing these errors. You might want to uninstall that particular extension from vscode. The link I provided should show you as to what that extension is and how it looks like.

[Talv]

@nspeedzy You do realize you've just posted on a bugtracker of said extension? No one here has any doubts as to what the cause is. It's more of a matter who's going to fix it. Because uninstalling it certainly does not count as such.

[ghost]

@Talv hmm ok

[reporter123]

A fix has been proposed at MR 12

[canadaduane]

@reporter123 Sorry, what's MR 12?

[rioj7]

@canadaduane I don't know where the 12 originates from @reporter123 but Pull Request #20 has a possible solution

[reporter123]

That's what I meant I have no idea how I got 12 in my head.