-
Notifications
You must be signed in to change notification settings - Fork 9
Issues: graphql/composite-schemas-spec
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Add pre-merge validation rule to ensure that there are no missing field arguments
#89
opened Dec 30, 2024 by
glen-84
External Argument Default Mismatch
specification doesn't account for all arguments
#78
opened Dec 19, 2024 by
danielreynolds1
The spec for
SelectedObjectField
doesn't seem to support the shorthand syntax
#74
opened Dec 16, 2024 by
glen-84
Improve counter-examples for "Enum Type Default Value Uses Inaccessible Value"
#69
opened Dec 16, 2024 by
glen-84
What term should we use for a federated gateway / router in this specification?
#17
opened Feb 1, 2024 by
martijnwalraven
Do we agree execution mechanisms are out of scope for this specification?
#16
opened Feb 1, 2024 by
martijnwalraven
Better terms for supergraph, subgraph and public API needed.
#11
opened Jan 23, 2024 by
michaelstaib
ProTip!
Exclude everything labeled
bug
with -label:bug.