Open Meemaw opened 1 month ago
TypedGraphQLError is used consistently across all error surfaces.
TypedGraphQLError
When using custom scalar, coercing exceptions (e.g CoercingParseLiteralException) don't use the TypedGraphQLError and provide very bare-bones errors.
This was improved in 8.6.0 for some validation errors, but custom scalar coercing was missed.
Note: A test case would be highly appreciated, but we understand that's not always possible
Thanks for flagging this. We'll fix this behavior in the next release or two .
Expected behavior
TypedGraphQLError
is used consistently across all error surfaces.Actual behavior
When using custom scalar, coercing exceptions (e.g CoercingParseLiteralException) don't use the
TypedGraphQLError
and provide very bare-bones errors.This was improved in 8.6.0 for some validation errors, but custom scalar coercing was missed.
Steps to reproduce
Note: A test case would be highly appreciated, but we understand that's not always possible