Use Schema types when generating docs for GraphQL deprecations
What does this MR do?
This MR builds on !56698 (merged) by using the new deprecation abstraction to generate documentation.
It also re-organizes the docs helper to make navigating it easier.
This MR is part of a sequence, aimed at adding the missing elements to the GraphQL documentation.
It is followed by !55944 (merged), which adds missing parts, and makes use of the new richer deprecation modelling.
As an intermediate stage, this MR makes sure we can call the deprecation object, and does some re-structuring of the rendering code.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
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
Edited by Alex Kalderimis