Skip to content

Provide "dry-run" functionality #114

@goanpeca

Description

@goanpeca

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 staletype::featurerequest for a new feature or capabilitytype::pocindicates some proof of concept or MVP work

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions