apollographql / apollographql/federation
Schema Composition allows defining @key field as different types in different federated services
Open
- Dominant language
- TypeScript
- Stars
- 725
- Forks
- 276
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 1
Description
Bug: Schema Composition allows defining @key field as different types in different federated services. This should probably be caught by schema composition as an error
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by tracing schema composition validation for @key fields across federated services; done means composition rejects differing @key field types with an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100