-
Notifications
You must be signed in to change notification settings - Fork 10
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
"Merge Union Types" should use an intersection and not a union for member types
#145
opened Jan 23, 2025 by
glen-84
Satisfiability validation rule for non-intersecting runtime types in different subgraphs
#140
opened Jan 16, 2025 by
dariuszkuc
Missing specification for merging interfaces implemented by objects and other interfaces
#137
opened Jan 16, 2025 by
glen-84
Behavior for
@inaccessible
and @internal
in combination with unions, interfaces and enum values.
#136
opened Jan 16, 2025 by
michaelstaib
Questions regarding the validation rule "Input With Missing Required Fields"
#117
opened Jan 8, 2025 by
glen-84
The spec for rule "Key Invalid Fields Type" doesn't handle multiple keys
#115
opened Jan 8, 2025 by
glen-84
Add validation rule to ensure that
@override(from:)
references an existing source schema
#114
opened Jan 7, 2025 by
glen-84
Update all validation rules to correctly handle
@inaccessible
/@internal
#109
opened Jan 6, 2025 by
glen-84
Add validation rule to prevent
@internal
and @shareable
from being used at the same time
#105
opened Jan 2, 2025 by
glen-84
Specify that arguments with require are treated as not existent in the merge process.
#99
opened Dec 31, 2024 by
michaelstaib
Validate that
@require
is correctly processed on arguments in validation
#98
opened Dec 31, 2024 by
PascalSenn
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.