CodeVetter · Repo Unpack · Extension points
TanStack/query
Extensions attach through options, callbacks, subscriptions, adapter primitives, and separate packages. Query and mutation functions are the main transport boundary, while persister contracts provide storage substitution. Manager setters allow environments and frameworks to replace event or scheduling behavior. Typed registration and ESLint rule tables supply compile-time and tooling extension mechanisms.
- Applications supply queryFn and mutationFn; query persisters wrap fetch execution, and QueryBehavior.onFetch can customize fetch context, with infinite queries selecting their built-in behavior.
- setQueryDefaults and setMutationDefaults register options by hashed keys; matching query defaults merge in registration order, so specific defaults should follow generic ones.
- Persister requires persistClient, restoreClient, and removeClient; the async storage factory accepts caller storage, key, throttle interval, serializers, and a retry callback that can transform or discard the snapshot.
- Dehydration supports query/mutation selection, data serialization, and pending-error redaction; hydration accepts deserialization and restored query/mutation defaults.
- focusManager.setEventListener and onlineManager.setEventListener replace environment listeners and clean up prior handlers; callers can also set focus or online state manually.
- createNotifyManager exposes setNotifyFunction, setBatchNotifyFunction, and setScheduler to integrate test wrappers, framework batching, and alternate scheduling.
- The Register interface supports declaration merging for defaultError, queryKey, mutationKey, queryMeta, and mutationMeta through core or adapter modules.
- Framework APIs build on shared observers, with Lit exporting query/mutation controllers and Angular exporting injection/provider features; lint extensions register rule modules in rules.ts and configure presets in index.ts.