Client

Use this role if you build GraphQL client libraries, frameworks, or SDKs.

Recommended practices

Once service capabilities are integrated into the GraphQL specification, some client behaviors should be driven by the server's exposed capabilities.

For servers that require trusted documents, the client must support them.

It's always recommended to address:

• Query componentization
• Cursor pagination

Capability-driven configuration

(Near future, hopefully!)

• Detect endpoint service capabilities and auto-configure client behavior: WebSockets, server-sent events, etc.
• Use capability negotiation to determine whether persisted documents are required, optional, or unsupported.
• If persisted documents are enabled, use capability metadata to discover publish and execute endpoints.
• Fall back safely when capabilities are absent or partial.