Skip to content
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.

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

Some TCK tests expect the 'data' response field when it shouldn't be there #579

Open
jmartisk opened this issue Nov 13, 2024 · 0 comments
Open

Comments

@jmartisk
Copy link
Contributor

https://spec.graphql.org/draft/#sec-Response-Format

If the request included execution, the response map must contain an entry with key data. The value of this entry is described in the “Data” section. If the request failed before execution due to a syntax error, missing information, or validation error, this entry must not be present.

So expecting data:null to be present in the response is against the GraphQL specification.

This affects at least invalidEnumValue, unknownQuery, unknownField, createNewNullNamedHero, createNewUnnamedHero, invalidDataTypeValue, unknownMutation

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

No branches or pull requests

1 participant