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
Is your feature request related to a problem? Please describe.
This is related to a recent change: #6191
We have a GraphQL service that is using business logic to expose user-friendly errors.
When moving to GraphQL federation, we want to keep those user-friendly errors, but I cannot find a good way to do so right now.
By default, error message are redacted.
If I activate include_subgraph_errors, then the router will expose too much information, like:
I cannot find a good way to tell the router to use the subgraph errors without adding internal information.
Describe the solution you'd like
We could have a flag to tell the router to only propagate subgraph errors, without adding more internal information.
Actually we could use include_subgraph_errors for that and add a sub-configuration to tell the router to add internal information.
Describe alternatives you've considered
Currently, we are using include_subgraph_errors, and we transform the error responses with one plugin.
First we were removing only the SUBREQUEST_HTTP_ERROR errors.
Now we need to also remove the added service field in the error extension.
I think we need a more straightforward solution.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This is related to a recent change: #6191
We have a GraphQL service that is using business logic to expose user-friendly errors.
When moving to GraphQL federation, we want to keep those user-friendly errors, but I cannot find a good way to do so right now.
By default, error message are redacted.
If I activate
include_subgraph_errors
, then the router will expose too much information, like:SUBREQUEST_HTTP_ERROR
errorservice
(PR)I cannot find a good way to tell the router to use the subgraph errors without adding internal information.
Describe the solution you'd like
We could have a flag to tell the router to only propagate subgraph errors, without adding more internal information.
Actually we could use
include_subgraph_errors
for that and add a sub-configuration to tell the router to add internal information.Describe alternatives you've considered
Currently, we are using
include_subgraph_errors
, and we transform the error responses with one plugin.First we were removing only the
SUBREQUEST_HTTP_ERROR
errors.Now we need to also remove the added
service
field in the error extension.I think we need a more straightforward solution.
The text was updated successfully, but these errors were encountered: