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

Add confirmation dialog for update all button #828

Closed
gep13 opened this issue Mar 18, 2021 · 9 comments
Closed

Add confirmation dialog for update all button #828

gep13 opened this issue Mar 18, 2021 · 9 comments
Labels
5 - Released The issue has been resolved, and released to the public for consumption Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Milestone

Comments

@gep13
Copy link
Member

gep13 commented Mar 18, 2021

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.

@gep13 gep13 added the Feature Issues that introduce new functionality to the project, instead of updating existing functionality label Mar 18, 2021
@gep13 gep13 added this to the 0.19.0 milestone Mar 18, 2021
@opusforlife2
Copy link
Contributor

Or the ability to cancel the operation?

@gep13
Copy link
Member Author

gep13 commented Mar 19, 2021

@opusforlife2 that work would be covered as part of a different issue, for example here:

#720

@opusforlife2
Copy link
Contributor

@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.

@gep13
Copy link
Member Author

gep13 commented Mar 19, 2021

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.

@opusforlife2
Copy link
Contributor

Ah. Got it.

gep13 added a commit that referenced this issue Apr 8, 2021
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.
@gep13
Copy link
Member Author

gep13 commented Apr 8, 2021

This has been implemented, and looks like the following:

image

@gep13 gep13 closed this as completed Apr 8, 2021
@opusforlife2
Copy link
Contributor

Awesome! Thank you so much! :D

@AdmiringWorm AdmiringWorm added the 4 - Done Code has been added to the repository, and has been reviewed by a team member label Jan 21, 2022
@gep13
Copy link
Member Author

gep13 commented Feb 10, 2022

🎉 This issue has been resolved in version 0.20.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

@corbob corbob added 5 - Released The issue has been resolved, and released to the public for consumption and removed 4 - Done Code has been added to the repository, and has been reviewed by a team member labels Sep 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 - Released The issue has been resolved, and released to the public for consumption Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Projects
None yet
Development

No branches or pull requests

4 participants