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
fix(cli): fix migration from globalShortcut to global-shortcut #9262
base: dev
Are you sure you want to change the base?
Conversation
…te-global-shortcut-and-skip-app.md
Ignoring all core modules allows for the command to be re-run multiple times without strange mutations.
Running `tauri migrate` more than once would wipe previously migrated capabilities.
…ti-run-migrate-and-package-names.md
)?; | ||
} else { | ||
log::info!( | ||
"Skipping capabilities migration; migrated capabilities found in {}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we also print the migrated capability json here? so the user can compare both files (or maybe write to migrates.json.tmp
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The established pattern so far has been to print any manual changes. Rather than a temporary file that the user is expected to act on, would it be better to check if migrated.permissions
is empty and, if not, make another file without the *:default
s?
Vector allocation and cloning is an expensive operation.
Reported in Discord: https://discord.com/channels/616186924390023171/731495028677148753/1221393137659023390.