URQL Patterns

Quick Guide: URQL is a small core plus a pipeline of exchanges, and almost every configuration question is really a question about that pipeline's order — synchronous exchanges before asynchronous ones, error handlers before what they catch, fetchExchange last. Caching is document-based by default, keyed on the query and its variables; normalized caching is an opt-in exchange. Hooks return a [result, execute] tuple, and the loading flag is fetching.

Detailed Resources:

• examples/core.md — client and provider, useQuery, mutations, error handling, per-query context
• examples/exchanges.md — the full pipeline, Graphcache config, auth with refresh, retry, custom exchanges
• examples/subscriptions.md — websocket setup, accumulating events, presence, cache updates from a subscription
• examples/v6-features.md — the GET default, preferGetMethod, and the v4 → v6 migration steps
• reference.md — request policy and cache method tables, CombinedError shape, exchange catalogue

Which path applies