Refactor container registry list page to grapqhl
What does this MR do?
This MR is one MVC step to refactor the container registry to use graphql, in particular here we are swapping vuex/axios for vue-apollo in the list page.
Plan
Description | MR |
---|---|
Swap axios/vuex for vue apollo on list page |
|
Swap axios/vuex for vue apollo on details page | TBD |
Remove vuex and move what is left to provide inject | TBD |
What changed beside the implementation
- The pagination is not keyset based, so we can only have
next/prev
and not the numbers anymore - Delete functionality is now enabled on the group page too and permissions are checked on per record basis
- The search is much snappier and fast
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry - [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
- [-] Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers - [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec
- [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Related to #276432 (closed)
Edited by Nicolò Maria Mezzopera