Draft: Fallback missing GraphQL fields to null
What does this MR do and why?
Fallback missing GraphQL fields to null
To prevent erros during rolling deploys when adding new fields, we fallback to a null value instead of returning a missing field error.
This only applies to queries made by our frontend application so that users using the API would still get errors when they make a typo.
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.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.