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'm going to close this because I think the router behavior seems correct and I'm not convinced we actually want to return the response from subgraphs in the way that the Gateway was doing it. In the future, we may want to consider exposing the HTTP-related details more specifically, but that always seemed like a bit of a leaky abstraction anyway.
I just tried to compare the router and the gateway's behavior if a subgraph returns an error:
CURL command:
gateway response:
router response:
The "response" field is missing in the router, I suspect it's because of the way we deal with errors in the
include_subgraph_errors
plugin.Originally posted by @o0Ignition0o in #1664 (comment)
The text was updated successfully, but these errors were encountered: