Skip to content

Make it clear that extra keys in the request/response payloads are not allowed #271

@benjie

Description

@benjie
Member

This is a task for myself really.

The extensions object exists so that vendors may add their own properties to requests/responses/errors/etc. All top-level keys are reserved by the spec. We should make this explicit, such that adding id as a key to a request automatically makes the request not a GraphQL-over-HTTP request. (Which is fine, because the server is still allowed to handle it however it sees fit.)

Activity

self-assigned this
on Oct 27, 2023
benjie

benjie commented on Oct 27, 2023

@benjie
MemberAuthor

(This relates to @martinbonnin's comments here: #264 (comment))

benjie

benjie commented on Oct 27, 2023

@benjie
MemberAuthor

Closing in favour of #278

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    Participants

    @benjie

    Issue actions

      Make it clear that extra keys in the request/response payloads are not allowed · Issue #271 · graphql/graphql-over-http