graphql graphql-spec issues

graphql / graphql-spec

GraphQL is a query language and execution engine tied to any backend service.

https://spec.graphql.org

14.31k stars 1.13k forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Uniqueness of field aliases

#1128 wutsch0 opened 4 days ago
1
When `sourceStream` errors, raise an error payload instead

#1127 benjie opened 4 days ago
2
GraphQL Subscriptions should handle errors in the source stream

#1126 benjie closed 4 days ago
2
nit: add rate limit extension example

#1125 sbilello opened 2 weeks ago
5
Spec edits for incremental delivery, Section 3 & 7 only

#1124 robrichard opened 3 weeks ago
1
Change 'original' to 'previous' to clarify multiple extensions

#1123 benjie opened 3 weeks ago
1
Make semantic non-null the default?

#1122 martinbonnin opened 3 weeks ago
0
Spec Bug...? ProvidedRequiredArgumentsRule fails to evaluate all potential runtime types

#1121 yaacovCR opened 3 weeks ago
18
Expand Deprecation Use Cases For Better Client Support and Service Support

#1119 gwardwell opened 1 month ago
4
Clarify 'Values of Correct Type' rule relates to literals

#1118 benjie opened 1 month ago
2
add __directive meta field parallel to __type

#1114 yaacovCR opened 2 months ago
6
Add note above variables to Values of Correct Type rule

#1113 yaacovCR closed 1 month ago
3
Error messages have non-standard capitalization and quote usage

#1112 yaacovCR closed 2 months ago
1
move Field Collection section earlier

#1111 yaacovCR closed 1 month ago
0
Incremental Delivery spec draft

#1110 robrichard opened 2 months ago
2
Fragment spread on interface type with no implementers

#1109 goto-bus-stop opened 3 months ago
7
add example for extensions as part of the response

#1108 sbilello closed 3 months ago
2
Add GraphQLConf 2024 banner

#1107 bignimbus closed 3 months ago
1
Allow empty object type _extensions_ in schema

#1106 ychescale9 opened 4 months ago
10
He

#1105 pineapplejuiice closed 4 months ago
0
Main

#1103 A385-cntrl closed 4 months ago
2
Define Data Collections used in the spec

#1102 benjie opened 4 months ago
1
Internal error occurred during message handling. Please check your implementation. Error: Subscription field must return Async Iterable. Received: undefined.

#1101 Phors-Stephen closed 5 months ago
1
chore: Update cspell.yml

#1100 Jason3S closed 5 months ago
4
Editorial changes for Event Streams

#1099 leebyron opened 5 months ago
3
Add 5.2.4 Operation Type Exists

#1098 Shane32 closed 1 month ago
4
No validation rule exists to assert mutation/subscription operations exist in the schema

#1097 Shane32 closed 2 months ago
5
Fixed unclear wording in the validation section

#1096 PascalSenn opened 6 months ago
1
REACT

#1095 aaron1234567890123 closed 6 months ago
0
Really

#1094 Heyitsquoracom closed 7 months ago
0
Hey

#1093 Heyitsquoracom closed 7 months ago
1
Recommend that order of unordered collections is maintained where possible

#1092 benjie opened 7 months ago
1
Define Data Collections used in the spec

#1091 benjie closed 4 months ago
4
Reformat the parts of an execution request

#1090 benjie closed 5 months ago
1
3.13 Directive validation edits

#1089 jbellenger opened 7 months ago
7
Add missing .

#1088 benjie closed 8 months ago
2
Consistently spell 'implementers'

#1087 benjie closed 5 months ago
1
[RFC] ID must always serialize as String would

#1086 benjie closed 8 months ago
2
Interface conditions fragments may not be used across spreads, discouraging reusability

#1085 duckki opened 8 months ago
2
Fix punctuation in grammar rule

#1084 benjie closed 5 months ago
4
Proposed spec changes for string literal aliases

#1082 cuhtis opened 9 months ago
9
Fragment arguments/variables (syntax/validation/execution)

#1081 JoviDeCroock opened 9 months ago
13
What must be the result of executing only one fragment on a list of union or interface type?

#1080 xperiandri opened 9 months ago
3
Unclear spec for array with fragments

#1079 njlr closed 9 months ago
1
chore: add clarifying note for composite and expand term

#1078 JoviDeCroock closed 5 months ago
8
Alternative spec implementation of deduplicated incremental delivery

#1077 yaacovCR closed 2 months ago
5
Composite types is not clearly defined

#1076 andimarek closed 5 months ago
1
RFC: support returning applied directives as part of the introspection

#1075 JoviDeCroock closed 5 months ago
10
[RFC] Implementation of June 2023 incremental delivery format with `@defer`

#1074 benjie opened 9 months ago
3
Be strict about error paths format

#1073 martinbonnin closed 7 months ago
7