The caught value. Non-object inputs are described, never stringified, since an arbitrary thrown value may itself be a payload.
Opt in to emitting the variables verbatim instead of
'[REDACTED]'. Development use only — see
GraphQLProviderConfigData.LogVariableValues. Note the message and stack
remain sanitised even when this is true, because the upstream copies
there are unbounded and unstructured; the opt-in returns the variables,
which is what a developer is actually asking for.
A structure safe to pass to console.error or a file logger.
Builds a log-safe diagnostic object for an error thrown by the GraphQL client.
The input error is never mutated — callers can and do continue to inspect and rethrow the original, so control flow that depends on it (JWT-expiry detection, upstream
catchblocks) is unaffected.