@beignet/react-query 0.0.23 → 0.0.25

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # @beignet/react-query
 
+## 0.0.25
+
+### Patch Changes
+
+- 7c83da7: Refresh package-shipped TanStack Intent skills to match current Beignet app structure, generators, route helpers, and React Query cache helpers.
+
+## 0.0.24
+
+### Patch Changes
+
+- 91bc9b5: Harden framework security defaults for generated tenancy, auth secrets, CORS,
+  body limits, uploads, devtools, OpenAPI, rate-limit IP sources, public storage,
+  and Meilisearch query fields.
+
 ## 0.0.23
 
 ### Patch Changes

package/README.md

@@ -23,8 +23,9 @@ This package requires TypeScript 5.0 or higher for proper type inference.
 
 This package ships a TanStack Intent skill for coding agents:
 `@beignet/react-query#client`. Load it when adding typed client setup, React
-Query options, feature client helpers, hooks, cache invalidation, server
-prefetching, or client/server boundary fixes in a Beignet app.
+Query options, infinite queries, feature client helpers, hooks, cache keys,
+cache invalidation, server prefetching, idempotent mutations, or
+client/server boundary fixes in a Beignet app.
 
 ## Setup
 
@@ -283,19 +284,19 @@ const rq = createReactQuery(apiClient);
 
 Headers are **excluded from generated query keys by default** because persisted
 caches would otherwise store credentials such as `Authorization` tokens. When a
-header changes response data — a tenant or workspace header, for example — opt
-that specific header into keys with `keyHeaders`:
+non-secret request-shaping header changes response data, opt that specific
+header into keys with `keyHeaders`:
 
 ```ts
 const rq = createReactQuery(apiClient, {
-  keyHeaders: ["X-Tenant-Id"],
+  keyHeaders: ["X-Workspace-Preview"],
 });
 
 rq(listTodos).queryOptions({
-  headers: { "X-Tenant-Id": "tenant-1", Authorization: "Bearer ..." },
+  headers: { "X-Workspace-Preview": "workspace-1", Authorization: "Bearer ..." },
 });
 // queryKey: ["beignet", "todos", "listTodos", "GET /todos",
-//   { headers: { "x-tenant-id": "tenant-1" } }]
+//   { headers: { "x-workspace-preview": "workspace-1" } }]
 ```
 
 Only whitelisted header names are included. Names are matched

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@beignet/react-query",
-  "version": "0.0.23",
+  "version": "0.0.25",
   "type": "module",
   "description": "TanStack Query integration for Beignet",
   "main": "./dist/index.js",

package/skills/client/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: client
-description: "Build Beignet browser client and TanStack Query integration with @beignet/react-query: createClient, createReactQuery, queryOptions, mutationOptions, cache keys, feature client helpers, hooks, QueryClientProvider, server prefetching, and client/server boundary fixes. Use when adding or debugging React Query usage in a Beignet app."
+description: "Build Beignet browser client and TanStack Query integration with @beignet/react-query: createClient, createReactQuery, queryOptions, mutationOptions, infiniteQueryOptions, cache keys and filters, feature client helpers, hooks, QueryClientProvider, server prefetching, idempotent mutations, and client/server boundary fixes. Use when adding or debugging React Query usage in a Beignet app."
 ---
 
 # Beignet React Query Client
@@ -98,10 +98,19 @@ Call server behavior through Beignet contracts and typed clients.
 - Use `queryOptions(...)` so options work with `useQuery`, `prefetchQuery`,
   `fetchQuery`, and server prefetching.
 - Use `mutationOptions(...)` with `useMutation`.
-- Use `rq(contract).invalidate(queryClient)` or the app's existing key helper
-  after successful mutations.
+- Use `infiniteQueryOptions(...)` with `useInfiniteQuery` for paginated
+  contracts. Prefer static `path`/`query` plus `page(...)`; if every page needs
+  fully dynamic params, pass a custom `key`.
+- Use `rq(contract).key(...)`, `filter(...)`, `contractFilter(...)`, and
+  `namespaceFilter(...)` when the app needs explicit cache keys or invalidation
+  filters.
+- Use `rq(contract).invalidate(queryClient, params?, options?)` or the app's
+  existing key helper after successful mutations.
 - If the app configures `createReactQuery(apiClient, { keyHeaders })`, preserve
   that when adding helpers so tenant or header-scoped caches stay distinct.
+- Contracts with idempotency metadata get one generated idempotency key per
+  `mutate(...)` variables object, stable across TanStack retry attempts. Pass
+  `idempotencyKey` in mutation variables only when the app must control it.
 - Keep business validation in use cases. Client validation is for UX and early
   feedback.