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 option to bypass confirmation dialogs of potentially destructive operations #919

Closed
65wat opened this issue Feb 16, 2022 · 2 comments · Fixed by #952
Closed

Add option to bypass confirmation dialogs of potentially destructive operations #919

65wat opened this issue Feb 16, 2022 · 2 comments · Fixed by #952
Assignees
Labels
5 - Released The issue has been resolved, and released to the public for consumption Improvement Issues that enhances existing functionality, or adds new features
Milestone

Comments

@65wat
Copy link

65wat commented Feb 16, 2022

Hello Chocolatey Team,

I’ve been using your software for a long time and really like it. However, recently I noticed that the GUI shows me an additional dialog when I’m trying to update all software. In 99% of my uses, that’s what I do with Chocolatey GUI (run it, let it refresh all packages, hit update all, done), so I kinda know what I’m doing (plays back Kimi Raikkonen radio message). I was wondering if you could add an option that would make it possible to skip the “Are you sure” dialog?

Cheers & have a great day

System Details

OS Build: 10.0.19044
Windows PowerShell version: 5.1
Chocolatey version: 0.12.1

@gep13
Copy link
Member

gep13 commented Feb 16, 2022

@65wat in the 0.20.0 release of Chocolatey GUI, we added confirmation dialogs to a few places, where the operation was potentially destructive, or where it is known that the operation could take a long time to complete:

Based on your feedback here, it seems like we need a feature, similar to Chocolatey's own allowGlobalConfirmation feature, which if enabled (it would be off by default) would by pass these checks.

I think this makes sense, and we could look to get this added in a future release.

@gep13 gep13 added this to the Future milestone Feb 16, 2022
@gep13 gep13 added 1 - Ready Issue is accepted, milestone added and are ready to be worked on Improvement Issues that enhances existing functionality, or adds new features labels Feb 16, 2022
@pauby pauby modified the milestones: Future, 1.1.0 Aug 24, 2022
@corbob corbob self-assigned this Aug 24, 2022
@corbob corbob added 2 - Working A user or team member has started working on the issue and removed 1 - Ready Issue is accepted, milestone added and are ready to be worked on labels Aug 24, 2022
corbob added a commit to corbob/ChocolateyGUI that referenced this issue Aug 25, 2022
corbob added a commit to corbob/ChocolateyGUI that referenced this issue Aug 25, 2022
corbob added a commit to corbob/ChocolateyGUI that referenced this issue Aug 25, 2022
Add option to skip modal confirmation dialogs for potentially
destructive operations. This somewhat matches AllowGlobalConfirmation in
Chocolatey CLI
@corbob corbob added 4 - Done Code has been added to the repository, and has been reviewed by a team member and removed 2 - Working A user or team member has started working on the issue labels Aug 25, 2022
@corbob corbob changed the title Add option to skip AreYouSureUpdateAllMessage Add option to bypass confirmation dialogs of potentially destructive operations Sep 7, 2022
@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 8, 2022
@choco-bot
Copy link

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

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 Improvement Issues that enhances existing functionality, or adds new features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants