Conversation
29177dd to
6584270
Compare
|
@sbatten Submenus seemed to work nicely in the editor context menu, but not across the rest of the workbench. There was some mixup with |
|
Very cool work 👏 |
| classNames.push('codicon'); | ||
| } | ||
|
|
||
| addClasses(this.element, ...classNames); |
There was a problem hiding this comment.
fyi - es6 deprecated, use this.element.classList...
There was a problem hiding this comment.
Actually didn't know that!
| case 'editor/title/context': return MenuId.EditorTitleContext; | ||
| case 'debug/callstack/context': return MenuId.DebugCallStackContext; | ||
| case 'debug/toolbar': return MenuId.DebugToolBar; | ||
| case 'debug/toolBar': return MenuId.DebugToolBar; |
There was a problem hiding this comment.
Yeah we had both for backwards compatibility, even though debug/toolbar was "deprecated". I am not sure if there are extensions which really on this.
There was a problem hiding this comment.
High risk. You could know relatively easy (telemetry, search extension usages) or just keep it given the low price of supporting it. btw: deprecated doesn't mean that we will remove it
There was a problem hiding this comment.
I just searched top 1000 extensions usages on debug/toolbar usage and only one extension used the deprecated name - the extension is not that popular and I have created an issue for them IBM-Blockchain/blockchain-vscode-extension#2593
So I suggest the following: let's go with the removal, and if needed we can easily reintroduce it as part of a recovery build if somebody complains.
fyi @weinand
|
@jrieken Thanks for the post-mergeum review! 🙏 |





This PR fixes #100172
SubmenuItemActionvsContextSubMenuconfusion