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
Is your feature request related to a problem? Please describe.
In my app, I'm using contribution point menus from the contrib module to let extensions contribute menu items.
Menu items must currently provided by JSON entries in the extension's package.json.
I have a top-level menu "View" with a submenu "Tool Views... >".
This submenu should be filled from the contributions to another contribution point, namely toolViews.
Therefore I need to programmatically add (or replace) JSON entries to (or in) the menus contribution point.
Describe the solution you'd like
Possible options
(1) Support an auto-fill marker in the specific submenus contribution point so the framework can generate the menu entries from contributions of another referenced contribution point.
(2) Support adding JSON contributions programmatically, e.g., provide a new registerJsonContribution or the like similar to registerCodeContribution .
(1) is more pragmatic and applies to that specific contrib point only
(2) is more generic and flexible
And (2) does not exclude (1).
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In my app, I'm using contribution point
menus
from thecontrib
module to let extensions contribute menu items.Menu items must currently provided by JSON entries in the extension's
package.json
.I have a top-level menu "View" with a submenu "Tool Views... >".
This submenu should be filled from the contributions to another contribution point, namely
toolViews
.Therefore I need to programmatically add (or replace) JSON entries to (or in) the
menus
contribution point.Describe the solution you'd like
Possible options
submenus
contribution point so the framework can generate the menu entries from contributions of another referenced contribution point.registerJsonContribution
or the like similar toregisterCodeContribution
.(1) is more pragmatic and applies to that specific contrib point only
(2) is more generic and flexible
And (2) does not exclude (1).
The text was updated successfully, but these errors were encountered: