-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): Update graphql
and related dependencies
#1200
Conversation
Is there any reason we'd want to continue supporting I'd like to get gateway supporting v16 asap, this seems like a good first step. Unfortunately there's a minor version bump in |
Updates on the TypeScript query planner changed the PlanningError structure, that will now always have an `extensions` field. No extensions are now expressed by having the extensions field value being null, or an empty Object. This PR allows us to express these requirements by: - Adding a new deserialize directive `none_only_if_value_is_null_or_empty_object`. - Applying the directive to the `PlanningError::extensions` field. - Adding comments and tests that make the new requirement more explicit.
I'm not qualified to judge the Rust stuff, but if it compiles, it's probably fine, right? Otherwise LGTM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving since Rust changes are approved already in #1149
Leaving this for @pcmanus or @martijnwalraven to merge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm as well.
No description provided.