louislam
Add update all button
Accidentally deleted the branch for #576
Tick the checkbox if you understand [x]:
- [x] I have read and understand the pull request rules.
Description
Adds an update all button to the stacks page as it can be frustrating to update when handling more than a small number of stacks
Type of change
Please delete any options that are not relevant.
- User interface (UI)
- New feature (non-breaking change which adds functionality)
Checklist
- [x] My code follows the style guidelines of this project
- [x] I ran ESLint and other linters for modified files
- [x] I have performed a self-review of my own code and tested it
- [x] My changes generate no new warnings
Screenshots (if any)
Hey, i have been using your image with this request merged and it works great, so thanks very much! Only thing missing for me is a feedback that the updates have started after you click the button, maybe a bottom right notification like the one for a finished update? What would also be cool is somthing like a "loading bar" that tells me the progress of the updates so you don't have to click through all to see if the updates are finished and you can reboot. But thats totally optional and not really needed for it to work well!
The updates start right when you click it. It doesn't go one by one 🙈
so clicking the update all button is literally like clicking all of the update buttons at the same time (that is the logic that happens underneth)
the only difference with the notification is that i added the scack name to the update completed one...
yeah i know but the user doesn't have any feedback that the button even works until the first update is finished and you get that notification, thats what confused me a bit at first, so a notification "Updates started" or something like that would help in my opinion :)
Came for this. It would be cool if there was an indicator so there IS an update available. But this would help too :-)
Came for this. It would be cool if there was an indicator so there IS an update available. But this would help too :-)
You should make a new issue for that 😉