Closed fhoeben closed 2 months ago
Thanks for the detailed report! I've got a fix in the works at #5090
@rmosolgo thanks for the fix we indeed get an error message now instead of an exception.
Could you take a look whether it would be possible to change the error to take into account what is actually expected according to the schema (like we get when passing -1
)? I now (2.3.16) get only a message and a location (no path). And the message is a bit more general than normally:
Expected a number, but it was malformed (\"-\")
I expected a path
to be present and a message like
Argument 'arg' on Field 'hello' has an invalid value (-foo). Expected type 'MyEnum!'.
Describe the bug
Queries containing incorrect argument values that start with a
-
do not result in a proper error message, but cause an exception to be raised.Versions
graphql
version: 2.3.14rails
(or other framework): N/A other applicable versions (graphql-batch
, etc) N/AGraphQL schema
GraphQL query
The following query works:
And the following incorrect query gives a correct error response:
Steps to reproduce
But when I send:
An exception is raised