[Breaking] fix(GRAPHQL): fix input coercing for integers and make them GraphQL spec complaint. #7584
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GraphQL spec doesn't allow any value apart from
integer
to be passed to a variable of typeInt
. So we are disallowing strings to be passed asInt
variables. Int64 is our own scalar data type, so we continue to acceptstring
andInteger
values for it.This PR allows passing
strings
toInt64
values when given directly in query/mutations and disallowsstring
to be passed toInt
in variables.So we will have below final behavior:
Int coercion rules in GraphQL spec:
https://spec.graphql.org/June2018/#sec-Int
This change is