Hi, in version 8.6.0, GraphQLJavaErrorInstrumentation was introduced which maps exceptions to TypedGraphqlError. However in the case of DataFetchingException when the error builder is used, the path parameter is not mapped and that information is therefore lost.
Expected behavior
The mapped TypedGraphqlError should contain path if the original exception contained path.
Actual behavior
The mapped TypedGraphqlError does not contain any path.
Steps to reproduce
Throw data fetching exception and let the instrumentation math it to GQL error
Note: A test case would be highly appreciated, but we understand that's not always possible
Hi, in version 8.6.0, GraphQLJavaErrorInstrumentation was introduced which maps exceptions to
TypedGraphqlError
. However in the case ofDataFetchingException
when the error builder is used, thepath
parameter is not mapped and that information is therefore lost.Expected behavior
The mapped
TypedGraphqlError
should contain path if the original exception contained path.Actual behavior
The mapped
TypedGraphqlError
does not contain any path.Steps to reproduce
Throw data fetching exception and let the instrumentation math it to GQL error
Note: A test case would be highly appreciated, but we understand that's not always possible