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

Added CLI flag to onlyUpdate shortcuts #1674

Merged
merged 1 commit into from
Oct 31, 2020

Conversation

vidia
Copy link

@vidia vidia commented Oct 22, 2020

By default, running with --createShortcut will create shortcuts in each specified location. Running it again after a user has explicitly deleted a shortcut will result in the shortcut being re-created. If the user has deleted one of these shortcuts, Squirrel should be able to optionally not recreate them in order to respect the user's decision to delete. Because the calculation of shortcut paths and details is handled within Squirrel, this should be handled by Squirrel itself rather than by Squirrel apps.

CreateShortcutsForExecutable has an option to "onlyUpdate" shortcuts (i.e. skipping if the shortcut does not already exist), this change exposes this option to the CLI as a flag.

This is intended to resurrect #1368 which has gone out of date.

This impacts the following issues: #1050, #831 and potentially enables a solution for multiple other shortcut related issues (see references in linked issues).

By default, running withcreateShortcut will create shortcuts in each specified location. If the user has deleted one of these shortcuts, it should optionally not be recreated. `CreateShortcutsForExecutable` has an option to "onlyUpdate" shortcuts (i.e. skipping if the shortcut does not already exist, this change esposes this option to the CLI as a flag.
@dylanclark
Copy link

Would also like to see this exposed, thanks for making a PR for this!

@anaisbetts anaisbetts merged commit 69a883d into Squirrel:develop Oct 31, 2020
@anaisbetts
Copy link
Contributor

👍 , thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants