Skip to content

fix: field selection set final values #1212

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

Merged
leebyron merged 4 commits into from
Apr 2, 2026
Merged

fix: field selection set final values #1212

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f9c82f6
fix: field selection set final values
MarkoMin Feb 24, 2026
2e728a4
Update spec/Section 2 -- Language.md
MarkoMin Feb 27, 2026
e44d837
feat: field subselection definition
MarkoMin Feb 27, 2026
0ecb37c
fix: md format
MarkoMin Mar 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec/Section 2 -- Language.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -419,8 +419,8 @@ discrete piece of information available to request within a selection set.
Some fields describe complex data or relationships to other data. In order to
further explore this data, a field may itself contain a selection set, allowing
for deeply nested requests. All GraphQL operations must specify their selections
down to fields which return scalar values to ensure an unambiguously shaped
response.
down to fields which return scalar or enum values to ensure an unambiguously
shaped response.
Comment thread
MarkoMin marked this conversation as resolved.
Outdated

For example, this operation selects fields of complex data and relationships
down to scalar values.
Expand Down