Skip to content

Clarify definition of response position - #1238

Open
benjie wants to merge 1 commit into
mainfrom
clarify-definition-of-response-position
Open

benjie wants to merge 1 commit into
mainfrom
clarify-definition-of-response-position

Conversation

@benjie

@benjie benjie commented Sep 10, 2026

Copy link
Copy Markdown
Member

:: A response position is a uniquely identifiable position in the response
data produced during execution. It is either a direct entry in the {resultMap}
of a {ExecuteSelectionSet()}, or it is a position in a (potentially nested) List
value. Each response position is uniquely identifiable via a response path.

The intention of response position is that it includes things that were elided by error propagation; e.g. if you query { a { b } } and b is non-null and throws, the result will be {a: null} but the error will have path ["a", "b"] indicating the a.b response position even though that position does not actually exist in the response.

(Also: ExecuteSelectionSet() doesn't exist any more.)

This PR clarifies the definition of response position to include these omitted values.

@benjie benjie added the ✏️ Editorial PR is non-normative or does not influence implementation label Sep 10, 2026
@netlify

netlify Bot commented Sep 10, 2026

Copy link
Copy Markdown

Deploy Preview for graphql-spec-draft ready!

Name Link
🔨 Latest commit 4df4224
🔍 Latest deploy log https://app.netlify.com/projects/graphql-spec-draft/deploys/6aa2b621c6fb5b000876e841
😎 Deploy Preview https://deploy-preview-1238--graphql-spec-draft.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@martinbonnin martinbonnin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

✏️ Editorial PR is non-normative or does not influence implementation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants