Draft: Move pipelines page to GraphQL - Part 9
What does this MR do and why?
Part one: !206072 (merged)
Part two: !207467 (merged)
Part three: !208865 (merged)
Part four: !209348 (merged)
Part five: !210021 (merged)
Part six: !209716 (merged)
Part seven: !210372 (merged)
Part eight: !211323
Part nine: YOU ARE HERE
In part nine we track down anything missing from the rest of the structured refactor and add it. When reviewing take a good look at app/assets/javascripts/ci/pipelines_page/pipelines.vue and then app/assets/javascripts/ci/pipelines_page/pipelines_graphql.vue and see if I've missed anything during the refactor. Thank you!
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
- First visit
Build > Pipelinesand ensure existing feature works as expected. - Next enable
Feature.enable(:pipelines_page_graphql)&&Feature.enable(:ci_pipeline_statuses_updated_subscription)feature flags - Visit
Build > Pipelinesagain - Test stuff and make sure it looks good
- Grep the codebase to make sure nothing is missing in the new refactor from
app/assets/javascripts/ci/pipelines_page/pipelines.vue
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #223264