Skip to content
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

Provide "force" or "replace" functionality #115

Open
2 tasks done
goanpeca opened this issue Feb 11, 2023 · 3 comments
Open
2 tasks done

Provide "force" or "replace" functionality #115

goanpeca opened this issue Feb 11, 2023 · 3 comments
Labels
stale::recovered [bot] recovered after being marked as stale type::feature request for a new feature or capability type::poc indicates some proof of concept or MVP work

Comments

@goanpeca
Copy link

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

@goanpeca goanpeca added the type::feature request for a new feature or capability label Feb 11, 2023
@jaimergp jaimergp added the type::poc indicates some proof of concept or MVP work label Feb 13, 2023
@jaimergp
Copy link
Contributor

A package update technically removes the shortcut as part of the uninstallation, so it should not collide? Where are you observing this? Are you running into conda/conda#11092 ?

Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Feb 14, 2024
@jaimergp
Copy link
Contributor

not stale

@github-actions github-actions bot added stale::recovered [bot] recovered after being marked as stale and removed stale [bot] marked as stale due to inactivity labels Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale::recovered [bot] recovered after being marked as stale type::feature request for a new feature or capability type::poc indicates some proof of concept or MVP work
Projects
Status: No status
Development

No branches or pull requests

2 participants