Skip to content

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.

Sign up for GitHub

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

11 Open 3 Closed
11 Open 3 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Inaccessible vs Inaccessible Type
#57 opened Nov 5, 2024 by smyrick
“Is” directive with mutually-exclusive arguments is smelly
#52 opened Sep 25, 2024 by gmac
2
Allow marking a key as deprecated
#51 opened Sep 11, 2024 by smyrick
2
Discuss the effect on public schema of @internal directive
#34 opened Apr 17, 2024 by kamilkisiela
4
Finding the right Batching Mechanism
#25 opened Mar 7, 2024 by michaelstaib
7
Composite Schemas vs. Distributed/Federated
#24 opened Feb 15, 2024 by martijnwalraven
2
More GraphQL native expression for FieldSelection?
#21 opened Feb 8, 2024 by JohnStarich
9
What term should we use for a federated gateway / router in this specification?
#17 opened Feb 1, 2024 by martijnwalraven
14
Do we agree execution mechanisms are out of scope for this specification?
#16 opened Feb 1, 2024 by martijnwalraven
3
Better terms for supergraph, subgraph and public API needed.
#11 opened Jan 23, 2024 by michaelstaib
1
12
Should entity resolvers be limited to the root level.
#8 opened Jan 23, 2024 by michaelstaib
1
ProTip! Find all open issues with in progress development work with linked:pr.