-
Notifications
You must be signed in to change notification settings - Fork 48
Open
Labels
stale::recovered[bot] recovered after being marked as stale[bot] recovered after being marked as staletype::featurerequest for a new feature or capabilityrequest for a new feature or capabilitytype::pocindicates some proof of concept or MVP workindicates some proof of concept or MVP work
Description
Checklist
- I added a descriptive title
- I searched open requests and couldn't find a duplicate
What is the idea?
The current API will raise an exception if a shortcut with the same name/location is already in place. It would be nice to have some sort of "force" functionality so that the command does not fail, and overwrites the found menu item with the new one.
Why is this needed?
In the context of updates of application packages, the package containing the menu might be the same for different versions, so having the ability to replace an existing menu with a new version without having to first delete the all one "manually" via the API would be benefitial.
What should happen?
Add a parameter to the create remove API could be an option.
Additional Context
No response
Metadata
Metadata
Assignees
Labels
stale::recovered[bot] recovered after being marked as stale[bot] recovered after being marked as staletype::featurerequest for a new feature or capabilityrequest for a new feature or capabilitytype::pocindicates some proof of concept or MVP workindicates some proof of concept or MVP work