apollographql / apollographql/federation

duplicate / identical types across subgraphs returns null results

Open
#2,989 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
725
Forks
276
Avg merge
1h 47m
Merged PRs (30d)
1

Description

### Issue Description

I've got **2 microservices** using federation and they both **share a common git submodule of `.graphql`** files.

The thing is: queries are not resolving due to them being duplicated in both subgraphs.

1. is it really intended behavior?
2. is there anything I can do, besides isolating queries?

Mutations are solving fine, even though they're duplicated as well...

I'm using NestJS on top of Apollo Federation.

### Link to Reproduction

https://stackoverflow.com/questions/72320648/apollo-gateway-duplicate-identical-types-across-subgraphs-returns-null-result

### Reproduction Steps

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the linked Stack Overflow reproduction and the shared .graphql schema files described in the issue. Compare the duplicated query and mutation behavior through the Apollo Federation gateway, then document whether the null result is intended and what workaround or fix is supported; no project test or source entry point is named.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.