Protected packages: Shorten GraphQL field `protectionRuleExists` Part 1
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 into master
What does this MR do and why?
- Based on the feedback from @10io, we decided to shorten the GraphQL field from "packageProtectionRuleExists" to "protectionRuleExists", see !146206 (comment 1871347682)
- Why? Because the GraphQl field is already defined in the context of packages
- This MR is a follow-up MR for Protected packages: Show protection info in pac... (!146206 - merged)
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 -
Wait for Protected packages: Show protection info in pac... (!146206 - merged)
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)
Realtes to #437928 (closed) and #437926
Edited by Gerardo Navarro