Honor new 'important' category of OutputEvents

[polinasok]

As a follow up to microsoft/debug-adapter-protocol#218, please highlight output messages tagged as 'important'. Perhaps log this in the console and trigger a showUser-like pop-up that disappears after a couple of moments?

[weinand]

@roblourens I've improved the output event support in Mock Debug. Now you can send output events for all output categories, e.g. prio(message) for "important" messages.

See https://github.com/microsoft/vscode-mock-debug/tree/main/sampleWorkspace#output-events

(since I haven't published a new release of Mock Debug to the market place, you will have to run out of source)

[roblourens]

I wonder whether these messages should also be marked somehow in the debug console?

[polinasok]

I wonder whether these messages should also be marked somehow in the debug console?

I think it's a great idea to have them stick out using something visual (bold font, different color or some other flag).

[weinand]

Yes, showing an important message in bold with a strong color (not red) makes sense.

@roblourens I've published a pre-release version (1.49.1) of Mock Debug to the Marketplace. It contains the "important category" support.

[roblourens]

@isidorn when I log an object, we ignore the category, why is that? I figure we should still show the "important" notification when logging an object

[weinand]

@roblourens I agree, we should not drop the category on logged objects.
Most likely, ignoring the category was an oversight.