-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Server: Validate remote schema queries #5938
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
Server: Validate remote schema queries #5938
Conversation
|
Deploy preview for hasura-docs ready! Built with commit 110475c |
abooij
left a comment
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.
Hi @codingkarthik, thanks for your improvements. The PR looks better. We're getting close, I think.
I am adding a few more items to discuss. It seems to me that this code will be playing an increasingly important role, and so I think it would be valuable if we go the extra mile with this PR.
abooij
left a comment
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.
Some minor code cleanups.
abooij
left a comment
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.
Awesome. Thanks for all the improvements, @codingkarthik!
|
Thank you so much @abooij for the review and for bearing with me :) |
tirumaraiselvan
left a comment
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.
changelog
Earlier, the graphql-engine just proxied the remote schema requests to the remote server without validation, the only validation that was done at the root level. This PR changes that behaviour by deeply parsing a query i.e validate every field and argument provided in a remote schema query
Description
Changelog
CHANGELOG.mdis updated with user-facing content relevant to this PR. If no changelog is required, then add theno-changelog-requiredlabel.Affected components
Related Issues
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sqlauto manages the new metadata through schema diffing?run_sqlauto manages the definitions of metadata on renaming?export_metadata/replace_metadatasupports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
querytypes:argspayload which is not backward compatibleJSONschemaGraphQL API
Schema Generation:
NamedTypeSchema Resolve:-
nullvalue for any input fieldsLogging
JSONschema has changedtypenames have changed