Refactor runner buttons into "action and button"
What does this MR do and why?
Refactor runner actions
This internal change splits the buttons component logic for pausing and deleting individual runners. So the resulting components can be reused in using a different appearance.
Splits mutation button components into delete action (with the mutation) and button (presentation).
For example, the delete action can now be used in presentations that are not buttons.
Why this change?
In #360429 (closed) our buttons will take the form of dropdown items depending on the layout, this decoupling allows us to add this new appearance.
Screenshots or screen recordings
List | Details |
---|---|
How to set up and validate locally
- Visit Admin -> Runners to see a list of runners
- Create 2 new runners
- You don't have to register them, just go back to the list after seeing
Runner created
- You don't have to register them, just go back to the list after seeing
- Visit Admin -> Runners and select the newly created runners
- Select Edit, Pause, and Delete to check the buttons in the list work
- Select the remaining runner
- Select Edit, Pause, and Delete to check the buttons in the details work
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #360429 (closed)
Edited by Miguel Rincon