Skip to content

Conversation

@rickbijkerk
Copy link
Contributor

@rickbijkerk rickbijkerk commented Dec 12, 2025

create failing test for the apollo router composition for the scenario in which you want to override a field annotated with @requires

…o in which you want to override a field annotated with @requires
@gemini-code-assist
Copy link

Summary of Changes

Hello @rickbijkerk, 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 introduces a new test case to __tests__/composition.spec.ts that specifically examines the interaction between Apollo Federation's @requires and @override directives. The test defines a scenario with three services where a field is both required from one service and overridden from another. The primary goal is to ensure that the Apollo Router can successfully compose a schema under these conditions, with the test asserting a successful composition.

Highlights

  • New Test Case for Directive Combination: A new test Using both @requires and @override has been added to __tests__/composition.spec.ts.
  • Validation of Apollo Federation Directives: This test specifically validates the composition behavior of Apollo Router when a field is simultaneously annotated with both @requires and @override directives.
  • Successful Composition Assertion: The test asserts assertCompositionSuccess, indicating that the combination of these directives in the defined scenario is expected to result in a valid, composable schema.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

…o in which you want to override a field annotated with @requires
Copy link

@gemini-code-assist gemini-code-assist bot left a 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 adds a new test case to verify that Apollo Router composition works correctly when a field is annotated with both @requires and @override. The test setup is good, but there's a large block of commented-out code that should be removed to improve readability and maintainability.

Comment on lines +108 to +158
let result = composeServices([
{
name: "a",
typeDefs: parse(/* GraphQL */ `
extend schema
@link(url: "https://specs.apollo.dev/federation/v2.3"
import: ["@key"]
)
type Query {
product(id:ID!): Product
}
type Product @key(fields: "id"){
id: ID!
title: String!
description: String!
}
`),
},
{
name: "b",
typeDefs: parse(/* GraphQL */ `
extend schema
@link(url: "https://specs.apollo.dev/federation/v2.3"
import: ["@key", "@external", "@requires"]
)
type Product @key(fields: "id"){
id: ID!
description: String! @external
calculatedField: String! @requires(fields: "description")
}
`),
},
{
name: "c",
typeDefs: parse(/* GraphQL */ `
extend schema
@link(url: "https://specs.apollo.dev/federation/v2.3"
import: ["@key", "@override", "@requires", "@external"]
)
type Product @key(fields: "id"){
id: ID!
description: String! @external
calculatedField: String! @requires(fields: "description") @override(from: "b")
}
`),
},
]);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This large block of commented-out code should be removed. It seems to be from a previous iteration of the test and is no longer needed, making the test harder to read.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant