-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Insights: graphql/graphql-spec
Overview
-
- 6 Merged pull requests
- 1 Open pull request
- 1 Closed issue
- 0 New issues
Could not load contribution data
Please try again later
6 Pull requests merged by 3 people
-
Clarify 'Values of Correct Type' rule relates to literals
#1118 merged
Apr 17, 2025 -
3.13 Directive validation edits
#1089 merged
Apr 17, 2025 -
3.10 Input Objects - clarify lists are permitted as Input fields
#1068 merged
Apr 17, 2025 -
Add 'extensions' to request
#976 merged
Apr 17, 2025 -
Consistently use 'response name' not 'response key'
#1147 merged
Apr 17, 2025 -
Rename field error to execution error; define response position
#1152 merged
Apr 17, 2025
1 Pull request opened by 1 person
-
Define "execution result" and "request error result"
#1159 opened
Apr 17, 2025
1 Issue closed by 1 person
-
Clarify "response key" vs "response name"
#1144 closed
Apr 17, 2025
5 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Replace `ExecuteSelectionSet` with `ExecuteGroupedFieldSet`
#1039 commented on
Apr 18, 2025 • 9 new comments -
Distinguish between executing (a selection set) vs processing (a response)
#1154 commented on
Apr 17, 2025 • 1 new comment -
[RFC] Implementation of June 2023 incremental delivery format with `@defer`
#1074 commented on
Apr 17, 2025 • 0 new comments -
Allow clients to disable error propagation via request parameter
#1153 commented on
Apr 17, 2025 • 0 new comments -
Clarify validation of custom scalar literals
#1156 commented on
Apr 17, 2025 • 0 new comments