Fix codebase to ensure the uniqueness of GraphQL fragment names
requested to merge 343999-fix-codebase-to-ensure-the-uniqueness-of-graphql-fragment-names into master
What does this MR do and why?
This MR enables the ESLint rule for unique GraphQL fragment names. We still need to leave some fragments with the same names in the codebase because we're using them for ee-else-ce scenario. These fragments have a linter rule disabled.
Screenshots or screen recordings
No visual changes
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 #343999
Edited by Natalia Tepluhina