Protected packages: Shorten GraphQL field `protectionRuleExists` Part 2
requested to merge gitlab-community/gitlab:437928-gerardo-navarro-protected-packages-show-protection-info-in-package-detail-page-follow-up-change-graphql-api-field-to-protection-rule-exists-part-2 into master
-
Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA
What does this MR do and why?
- Uses the shortened GraphQL field
protectionRuleExistsin the frontend instead ofpackageProtectionRuleExists - Follow-up MR for !151881 (merged)
- Splitting up the MR was suggested here and here
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
MR Checklist (@gerardo-navarro)
-
Changelog entry added, if necessary -
Documentation created/updated via this MR -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the javascript style guides -
Conforms to the database guides
Screenshots or screen recordings
No visual or UX changes in the frontend. This MR only renames a graphql field name.
How to set up and validate locally
Follow the same steps as described in !146206 (merged)
Edited by Gerardo Navarro