Currently, this page generates JSON for the chrome_menu UX page property. Extend this page to generate JSON for the chrome_menu_actions UX Page Property as well.
I'm not sure what this will entail, but you must make sure you do not impede current functionality. At a minimum, what I think needs to be implemented:
- Add a Toggle/Switch to select which type of menu you are generating in the Start Container
- Saved Menu Container should show both types of menus
MenuBuilderUtils Client Script Include needs to be updated to generate the JSON for this property. Will probably also need to add new client state parameters to the page?
Menu Builder GraphQL API and Get Menus / Save Menu Data Brokers are used to get and save existing chrome_menu menus. This functionality needs to be duplicated for chrome_menu_actions menus.
- The issue on the sister repository will add new functionality to the component, like dispatching a new event. The page needs to be updated to respond to the new event and any other changes from the component to support this new feature.
Currently, this page generates JSON for the
chrome_menuUX page property. Extend this page to generate JSON for thechrome_menu_actionsUX Page Property as well.I'm not sure what this will entail, but you must make sure you do not impede current functionality. At a minimum, what I think needs to be implemented:
MenuBuilderUtilsClient Script Include needs to be updated to generate the JSON for this property. Will probably also need to add new client state parameters to the page?Menu BuilderGraphQL API andGet Menus/Save MenuData Brokers are used to get and save existingchrome_menumenus. This functionality needs to be duplicated forchrome_menu_actionsmenus.