-
Couldn't load subscription status.
- Fork 3
fix(query-planner, router): fix introspection for federation v1 supergraph #526
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
Conversation
Summary of ChangesHello @dotansimha, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses critical introspection resolution errors that occurred because the consumer-facing schema was not fully filtering out certain internal GraphQL elements. Specifically, Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
c818e11 to
6f168e2
Compare
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.
Code Review
This pull request correctly addresses an introspection error by adding missing filters for federation-specific schema elements. The changes are logical and well-implemented. I've pointed out a leftover debugging statement that should be removed and suggested a minor code simplification for better readability.
6f168e2 to
08576c7
Compare
✅
|
|
🐋 This PR was built and pushed to the following Docker images: Image Names: Platforms: Image Tags: Docker metadata{
"buildx.build.ref": "builder-6103cb8a-9c9b-4b38-bdf6-6f16336b8e37/builder-6103cb8a-9c9b-4b38-bdf6-6f16336b8e370/j5lnpjjxsubpo1ejek83coeoa",
"containerimage.descriptor": {
"mediaType": "application/vnd.oci.image.index.v1+json",
"digest": "sha256:61332a10238cdb08155cbc9850a59b524eee90912ac5304f63d7f8ca3e6c22f0",
"size": 1609
},
"containerimage.digest": "sha256:61332a10238cdb08155cbc9850a59b524eee90912ac5304f63d7f8ca3e6c22f0",
"image.name": "ghcr.io/graphql-hive/router:pr-526,ghcr.io/graphql-hive/router:sha-78a3864"
} |
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.
Do you think we should add some tests to make sure the supergraph variant that has core__x definitions?
The consumer-facing schema was missing filtering for
enum core__Purpose,directive @core, anddirective @join_owner. This caused introspection errors due to failure to find other associated types.