Skip to content
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

fix: strip @external fields in interface extensions #2848

Merged

Conversation

lennyburdette
Copy link
Contributor

Before this change, including an external field in an interface
extension would fail composition in the gateway with an error:

Field "Product.id" already exists in the schema. It cannot also be defined in this type extension.

@apollo-cla
Copy link

@lennyburdette: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

Copy link
Contributor

@JakeDawkins JakeDawkins left a comment

Choose a reason for hiding this comment

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

Thanks so much! Just one slight change, and should be good to go 👍

packages/apollo-federation/src/composition/utils.ts Outdated Show resolved Hide resolved
Before this change, including an external field in an interface
extension would fail composition in the gateway with an error:

```
Field "Product.id" already exists in the schema. It cannot also be defined in this type extension.
```
@JakeDawkins JakeDawkins merged commit c883224 into apollographql:master Jun 17, 2019
abernix pushed a commit to apollographql/federation that referenced this pull request Sep 4, 2020
…ollo-server#2848)

Before this change, including an external field in an interface
extension would fail composition in the gateway with an error:

```
Field "Product.id" already exists in the schema. It cannot also be defined in this type extension.
```
Apollo-Orig-Commit-AS: apollographql/apollo-server@c883224
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants