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
Fix issues in Error Handling not identifying GraphQL Server errors correctly in all cases, and therefore not propagating the full details returned by the Server. We now check all response contents (if available) if it looks like Json and then interrogate it for the existence of an errors property and parse all details if possible. Also fixed issue not processing the error path variables correctly (int vs long return values); we now handle all possible numeric types.
//Because this may be a result from a non-200-OK request response we attempt to inspect the response payload and possibly parse out
29
34
// error details that may be available in the Error Response Content (but not already parsed and available (e.g. when GraphQL responds with 400-BadRequest).
$"[{(int)httpStatusCode}-{httpStatusCode}] The GraphQL server returned an error response for the query."
368
+
+" This is likely caused by a malformed/non-parsable query, or a Schema validation issue; please validate the query syntax, operation name, and arguments"
369
+
+" to ensure that the query is valid.",this.GraphQLQuery,errorContent,httpStatusCode,httpException
<Description>GraphQL client extensions for Flurl.Http -- lightweight, simplified, asynchronous, fluent GraphQL client API extensions for the amazing Flurl Http library!</Description>
0 commit comments