-
Notifications
You must be signed in to change notification settings - Fork 4
test: Populate entity's external fields in E2E inventory subgraph #603
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 @enisdenjo, 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 an issue where external fields of federated entities, such as 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
|
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 populates the external price and weight fields in the inventory subgraph's entity resolver. This fixes an issue where shippingEstimate was always null in E2E tests, which could lead to false negatives. The changes to the test snapshots reflect this fix. I've added one suggestion to improve the robustness of the entity resolver in bench/subgraphs/inventory.rs by handling cases where a product might not be found, preventing potential panics during tests.
✅
|
|
🐋 This PR was built and pushed to the following Docker images: Image Names: Platforms: Image Tags: Docker metadata{
"buildx.build.ref": "builder-a44c9769-e1a1-4ea7-88b4-db50ffe8dcdb/builder-a44c9769-e1a1-4ea7-88b4-db50ffe8dcdb0/jx2pcr1jm4imd9fo9tpnu0y2p",
"containerimage.descriptor": {
"mediaType": "application/vnd.oci.image.index.v1+json",
"digest": "sha256:331e918cafd443c836f712857c03280f4510dc77ff8f3bb3f3edb5f551d6be36",
"size": 1609
},
"containerimage.digest": "sha256:331e918cafd443c836f712857c03280f4510dc77ff8f3bb3f3edb5f551d6be36",
"image.name": "ghcr.io/graphql-hive/router:pr-603,ghcr.io/graphql-hive/router:sha-1cdb70e"
} |
The
shippingEstimatewas always returning null even though it should not. Could lead to false-negatives in tests.https://async-graphql.github.io/async-graphql/en/apollo_federation.html#requires
P.S. Fixed in benchmarks repo too graphql-hive/graphql-gateways-benchmark#894.