You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once started up, the extension creates two output channels with the same name (without a warning or a runtime error). The latter channel is shown and the output channel switcher doesn't allow selecting the former one, it always switches to the latter one.
There is a couple of ways this could be fixed:
Throw a runtime error while trying to open up a channel with the same name again (this is risky as multiple extensions can create the same channel name and I don't know if VS Code prefixes the channel names internally or if this would open up a way to crash another extension).
Show already existing channel by the given name. This is my preference as it would make it simple to create channels on demand and just call createOutputChannel each time without having to keep track of whether the channel is already created. There is no API for enumerating (even own) channels, so this would be a behaviour that much nicer.
The text was updated successfully, but these errors were encountered:
Steps to Reproduce:
Create an extension which does this in its
activate
method:Once started up, the extension creates two output channels with the same name (without a warning or a runtime error). The latter channel is shown and the output channel switcher doesn't allow selecting the former one, it always switches to the latter one.
There is a couple of ways this could be fixed:
Throw a runtime error while trying to open up a channel with the same name again (this is risky as multiple extensions can create the same channel name and I don't know if VS Code prefixes the channel names internally or if this would open up a way to crash another extension).
Show already existing channel by the given name. This is my preference as it would make it simple to create channels on demand and just call
createOutputChannel
each time without having to keep track of whether the channel is already created. There is no API for enumerating (even own) channels, so this would be a behaviour that much nicer.The text was updated successfully, but these errors were encountered: