Advanced

React NativeCopy Anchor Link

The vanilla client needs a working fetch implementation. Pass one as the second argument to FetchTransport if your runtime does not provide a compatible global fetch.

Use an API URL reachable from the device. On a physical device, localhost refers to the device, not your development computer. Verify TLS and the platform's network policy. The React adapter also needs its matching React Query dependency and provider setup.

Custom serversCopy Anchor Link

Use the 0.3.0 Axum adapter source as a protocol reference. An adapter must create context, decode input, dispatch the correct operation kind, encode the result envelope, and handle errors. Subscriptions also need IDs, cancellation, and connection cleanup.

The internal execution API is not a stable interface. Pin the rspc version and test your adapter with the exact client package you deploy.

Custom transports, not linksCopy Anchor Link

The tuple client uses a Transport with doRequest(operation, key, input). Its subscription support also uses a client callback for incoming events. There is no finished public link-chain API in this client generation.

If you implement a transport, preserve error behavior and subscription cleanup. Do not replace transport code merely to add a header; FetchTransport already accepts a custom fetch function.

Invalidate a queryCopy Anchor Link

Use your frontend query library to invalidate cached data after a successful mutation. With TanStack Query v5, the shape is:

await client.mutation(["updateUser", input]);
await queryClient.invalidateQueries({ queryKey: ["getUser", input.id] });

This assumes those procedures exist. Match the exact key used when reading the data. Invalidation is not pushed automatically by the 0.3.0 server.