graphql / graphql/graphql-spec

Nullable variables field in request payload

Open
#483 4 comments 0 reactions 0 assignees View on GitHub
💤 stale ? 🤷‍♀️ Ambiguity
Dominant language
JavaScript
Stars
14.6k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

It looks like the specification is not clear if the client provides a request without variables, does the field "variables" should be assigned "null" or "{}" or both are valid?

Context:
In the [altair](https://altair.sirmuel.design) tool, the default value is set to "{}" (without the double quotes) and in the graphql-java implementation, it's expecting a "null" value if not variables are needed. The result is, the queries are rejected on the server side, so does the server side is too stick or is it the client side which is providing the wrong value?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.