graphql/composite-schemas-spec

View on GitHub

GraphQL Composite Schema specification

Stars: 54
Forks: 15
Open beginner issues: 0
Indexed issues: 48

Dominant language: Shell
License: MIT
Last GitHub push: Aug 7, 2026
Latest indexed: Sep 17, 2026
Contributing guide: Contributing guide
Code of conduct: No code of conduct
Beginner labels: No beginner labels indexed
PR merge metrics: No merged PRs in 30d

Open All

48 open issues indexed

Do we agree execution mechanisms are out of scope for this specification? Open

triaged

graphql/composite-schemas-spec#16 · 4 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
What term should we use for a federated gateway / router in this specification? Open

graphql/composite-schemas-spec#17 · 14 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Composite Schemas vs. Distributed/Federated Open

graphql/composite-schemas-spec#24 · 2 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Finding the right Batching Mechanism Open

triaged

graphql/composite-schemas-spec#25 · 10 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Allow marking a key as deprecated Open

graphql/composite-schemas-spec#51 · 3 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Inaccessible vs Inaccessible Type Open

discussion-wg

graphql/composite-schemas-spec#57 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Add validation rule no local requirements Open

triaged

graphql/composite-schemas-spec#66 · 1 comment · 0 reactions · 2 assignees · Indexed Sep 17, 2026
Improve counter-examples for "Enum Type Default Value Uses Inaccessible Value" Open

triaged

graphql/composite-schemas-spec#69 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Align spec language in `ValidateDefaultValue` Open

triaged

graphql/composite-schemas-spec#72 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Specify that a source schema must have a unique name. Open

graphql/composite-schemas-spec#88 · 3 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Interface Merge Behaviour Open

area: interface-object

graphql/composite-schemas-spec#90 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Specify that arguments with require are treated as not existent in the merge process. Open

triaged

graphql/composite-schemas-spec#99 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Add validation rule to prevent `@internal` and `@shareable` from being used at the same time Open

triaged

graphql/composite-schemas-spec#105 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Update all validation rules to correctly handle `@inaccessible`/`@internal` Open

triaged

graphql/composite-schemas-spec#109 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Issues with the "Override Source Has Override" specification Open

triaged

graphql/composite-schemas-spec#113 · 2 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Add validation rule to ensure that `@override(from:)` references an existing source schema Open

triaged

graphql/composite-schemas-spec#114 · 3 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
The spec for rule "Key Invalid Fields Type" doesn't handle multiple keys Open

triaged

graphql/composite-schemas-spec#115 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Questions regarding the validation rule "Input With Missing Required Fields" Open

triaged

graphql/composite-schemas-spec#117 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
How should `@external`work exactly Open

discussion-wg

graphql/composite-schemas-spec#127 · 5 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Evaluate More Specific Scalars for Directives Open

graphql/composite-schemas-spec#128 · 1 comment · 0 reactions · 1 assignee · Indexed Sep 17, 2026
clarify merge order Open

graphql/composite-schemas-spec#132 · 7 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Behavior for `@inaccessible` and `@internal` in combination with unions, interfaces and enum values. Open

triaged

graphql/composite-schemas-spec#136 · 4 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Missing specification for merging interfaces implemented by objects and other interfaces Open

discussion-wg

graphql/composite-schemas-spec#137 · 1 comment · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Satisfiability validation rule for non-intersecting runtime types in different subgraphs Open

triaged

graphql/composite-schemas-spec#140 · 1 comment · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Miscellaneous feedback regarding the merge stage spec text Open

triaged

graphql/composite-schemas-spec#142 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Add validation rule for @lookup in invalid location Open

triaged

graphql/composite-schemas-spec#144 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
referencing fields with @require that specify arguments Open

discussion-wg

graphql/composite-schemas-spec#146 · 2 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Questions regarding post-merge validation rules Open

triaged

graphql/composite-schemas-spec#147 · 4 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
The "External Unused" rule lacks complex examples Open

triaged

graphql/composite-schemas-spec#151 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Issues with `Implemented by Inaccessible` Open

triaged

graphql/composite-schemas-spec#154 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Extra stage at the beginning named "Parse Source Schemas"? Open

discussion-wg

graphql/composite-schemas-spec#167 · 1 comment · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Proposal: Simplified Key Definition in GraphQL Composite Schemas Open

discussion-wg

graphql/composite-schemas-spec#168 · 4 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Miscellaneous feedback regarding FieldSelectionMap scalar validation Open

triaged

graphql/composite-schemas-spec#171 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Support for the Relay spec and Node interface Open

area: relay triaged

graphql/composite-schemas-spec#178 · 1 comment · 1 reaction · 1 assignee · Indexed Sep 17, 2026
Add appendix/specification for `FieldSelectionSet` scalar Open

triaged

graphql/composite-schemas-spec#183 · 0 comments · 0 reactions · 1 assignee · Indexed Sep 17, 2026
Consider rewriting the algorithms for "* Invalid Fields" to work with the composite schema Open

needs-more-information

graphql/composite-schemas-spec#184 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Optional? comma to separate SelectedObjectField in FieldSelectionMap Open

triaged

graphql/composite-schemas-spec#187 · 3 comments · 3 reactions · 1 assignee · Indexed Sep 17, 2026
Test Framework Proposal Open

graphql/composite-schemas-spec#195 · 2 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Proposal: Spec-suggested internally deferring of fields and/or `@splitSchema` Open

graphql/composite-schemas-spec#198 · 2 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Proposal: Simplifying enum merging via `@inputOnly` and `@outputOnly` Open

graphql/composite-schemas-spec#202 · 4 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Merging of @deprecated directives Open

graphql/composite-schemas-spec#203 · 2 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Add validation rule FIELD_ARGUMENT_DEFAULT_MISMATCH Open

graphql/composite-schemas-spec#209 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
`@oneOf` input object type merging Open

graphql/composite-schemas-spec#214 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Add validation rule to warn on differing `@specifiedBy` URLs Open

graphql/composite-schemas-spec#216 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Add spec for merging `specifiedByURL` Open

graphql/composite-schemas-spec#217 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Interest from the Python ecosystem (Ariadne) / Current status & how can we help? Open

graphql/composite-schemas-spec#219 · 3 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Open question I stumbled across while implementing feddi-gateway Open

graphql/composite-schemas-spec#222 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Validation rule: non-deprecated field referencing a deprecated object type Open

graphql/composite-schemas-spec#236 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

graphql/composite-schemas-spec

Get new issues in your inbox