You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find this example to be impossible as the String Input Coercion does not allow for anything other than string inputs and the Int Input Coercion does not allow for anything other than Int inputs.
This type change would make sense if it was a return value, but it is an input, which is very rigid.
Also, if the Input Object Type Validation could be updated to include a comment about nullish values, that would be great.
Thank you,
Barret
The text was updated successfully, but these errors were encountered:
This section had some redundancy and confusing statements in addition to some outdated examples for coercing field values.
This rewrite expands on the examples and consolidates the coercion rules.
Fixes#272Closes#311
This section had some redundancy and confusing statements in addition to some outdated examples for coercing field values.
This rewrite expands on the examples and consolidates the coercion rules.
Fixes#272Closes#311
Hello,
Great document! Thank you!
I am parsing my way through the Input Object, Input Coercion section. It states input definition of
and says an input of
can be coerced into
.
I find this example to be impossible as the String Input Coercion does not allow for anything other than string inputs and the Int Input Coercion does not allow for anything other than Int inputs.
This type change would make sense if it was a return value, but it is an input, which is very rigid.
Also, if the Input Object Type Validation could be updated to include a comment about nullish values, that would be great.
Thank you,
Barret
The text was updated successfully, but these errors were encountered: