Console

Knowledge / GraphQL Errors Your Widgets Should Ignore

2026-02-04 · Elena Costa

GraphQL Errors Your Widgets Should Ignore

Boundary layers between ferry clients and presentation code, with typed fallbacks.

Server room corridor with cool linear lighting
GraphQL Architecture Dart

Widgets should not parse GraphQL error payloads. We generate a narrow Result type that collapses transport failures, partial data, and auth redirects into three explicit branches the UI team can theme consistently.

Partial data is the trickiest branch. We require product owners to declare which fields are safe to render when siblings fail. That declaration lives next to the query document so codegen stays honest when fields rename.

Auth redirects deserve their own navigator observer rather than scattering checks inside every repository. Centralizing reduces duplicate snackbars that train users to ignore warnings.

Telemetry tags each error branch with a cohort-safe code—no raw stack traces in analytics. Support staff correlate using the ticket id surfaced in-app, keeping PII out of dashboards.

Back to field notes