-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API: submenus extension point #102784
API: submenus extension point #102784
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 👏 |
} | ||
|
||
addClasses(this.element, ...classNames); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fyi - es6 deprecated, use this.element.classList...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually didn't know that!
@@ -47,16 +47,15 @@ namespace schema { | |||
case 'explorer/context': return MenuId.ExplorerContext; | |||
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API breakage?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jrieken Thanks for the post-mergeum review! 🙏 |
This PR fixes #100172
SubmenuItemAction
vsContextSubMenu
confusion