Update backend graphql feature flag docs
What does this MR do and why?
This updates the backend docs to compliment the frontend doc graphQL guideline changes.
Problem Summary
More details in the issue for this MR. #342998 (closed)
When using the @include
or @skip
directive from frontend in conjunction with a feature flag, and the backend resolver also uses the same feature flag and the feature_flag property
We get an exception due to a schema mismatch. This MR updates the backend guidelines and suggests an alternative approach for this edge case.
Frontend graphQL feature flag doc changes:
Backend graphql feature flag issue:
Example of the suggested workaround in action: !69661 (diffs)
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
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 #342998 (closed)