Fix graphql resolver complexity
What does this MR do?
Since 1.9 graphql always sets complexity for resolvers, which caused that our default resolver complexity proc wasn't used.
Unless complexity is set explicitly then graphql now uses complexity
1. To avoid this behavior, we use complexity method to set
complexity to 0, then when instantiating a field we use our
default complexity proc if complexity is 0.
Related to #35736 (closed)
Screenshots
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