-
Notifications
You must be signed in to change notification settings - Fork 47
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 (and in development?) API supports the ability to create and remove shortcuts by pointing to a path or providing a dictionary of metadata.
Why is this needed?
In some cases it is nice to know what will happen without actually running the creation or removal process.
What should happen?
Provide a parameter or flag so that the result of create/remove is the same, but without actually executing the process of creation or removal in a similar vein to the "--dry-run" functionality of condaProvide a parameter or flag so that the result of create/remove is the same, but without actually executing the process of creation or removal in a similar vein to the "--dry-run" functionality of conda
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