Notifications - show which extension they came from

[roblourens]

Sometimes notification messages appear, and it isn't clear whether they are from vscode or an extension, and if so, which one. Right now I sometimes see "The internet connection appears to be offline" and don't know which extension is responsible. It would be useful to be able to easily trace the message to an extension, maybe with a tooltip on the message that shows the originating extension's name. It looks like a notification UX overhaul is on the way, #1135.

[jrieken]

I like, we already to that for status bar messages

[jrieken]

I postpone this until we get the new notification story in place

[ryh]

Could you tell us which API for extension can send the message.
some FUNCTION called showInformationMessage or just showInformationMessage ?

[jrieken]

@bpasero Given that this annoys people is there something the message service can do with ease?

[bpasero]

@jrieken so for the status bar you were talking about this right?

Our notification UX needs an overhaul (we started to revisit this recently but it needs more thinking - @stevencl fyi) and so we have only limited amount of things we can do in the UI.

A couple of ideas

• add another button at the end of each message that comes from an extension to "Manage" that extension (a bit ugly because it makes the whole thing even more complicated)
• prefix the message with the name of the extension (e.g. [TypeScript] bla bla)
• decorate the message in some way that its clear the message is from an extension (maybe with the prefix as stated before):

We should do something pragmatic and simple given that this UI is throwaway code anyways.

[jrieken]

To begin with, I have added a source attribute that show on hover....

[jrieken]

Refined this to show the extension id along the extension name and to also show the hover on the severity label

[sandy081]

@jrieken I think it has to be extension display name instead of extension.name. extension id is nothing but ${publisher_id}.${extension.name}. Showing extension name again is redundant.

Shall I file a separate issue or reopen this?

[jrieken]

@sandy081 Please make a separate issue, thanks