-
Notifications
You must be signed in to change notification settings - Fork 255
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
Add confirmation dialog for update all button #828
Comments
Or the ability to cancel the operation? |
@opusforlife2 that work would be covered as part of a different issue, for example here: |
@gep13 I know. That's my issue. :P What I was suggesting is that this doesn't need to be implemented if the ability to cancel already exists. |
I understand your point, and I was aware that it was your issue. The main reason that I created this issue, with the links to the other ones, is for consistency. When starting an operation that is potentially destructive, or which may take a long time to complete, a modal window asking whether the user is sure makes sense. We already have some modals for the operations that can be performed on the setting screen, so adding them into each of the listed issues, brings consistency to the application. Then later, for the longer running processes we should introduce the ability to cancel the operation. This has to be done in such a way that it doesn't "break" anything, as we wouldn't want an installation/upgrade to end abruptly, and leave the package in a broken state. That is why it is a different scope of work. |
Ah. Got it. |
Due to the fact that the action of updating all packages, depending on the current number of outdated packages, can take a long time to complete, we should prompt the user to confirm whether they want to continue or not.
Awesome! Thank you so much! :D |
🎉 This issue has been resolved in version 0.20.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
This operation can potentially take a long time, and we should confirm with the user as to whether they really want to do this right now.
The text was updated successfully, but these errors were encountered: