@lotics/app-sdk 0.87.5 → 0.87.7

package/dist/src/hooks.js

@@ -71,6 +71,14 @@ function swrConfig(revalidateOnFocus) {
         revalidateOnFocus,
         revalidateOnReconnect: revalidateOnFocus,
         shouldRetryOnError: false,
+        // A query's KEY carries its params, filter and sort, so anything derived
+        // from the rows on screen re-keys the moment they change. Without this SWR
+        // answers a new key with `undefined`, `rows` falls to `[]`, and every list
+        // renders empty for a frame — unmounting each row's images, which remount
+        // blank. That is the behaviour the `loading` contract above already
+        // promises against, and what the product app sets globally for the same
+        // reason.
+        keepPreviousData: true,
     };
 }
 /**
@@ -289,9 +297,7 @@ export function usePaginatedQuery(alias, params, opts) {
         offset: page * pageSize,
         sort,
         filter,
-    }), 
-    // Keep the previous page's rows on screen while the next page loads.
-    { keepPreviousData: true, ...swrConfig(revalidateOnFocus) });
+    }), swrConfig(revalidateOnFocus));
     // Not counted when the caller supplies the total, when the hook is disabled,
     // or under a fixture — see `useCountRead` for why the key drops page and sort.
     const countSwr = useCountRead(alias, params, filter, !mockRows && enabled && !callerOwnsTotal, revalidateOnFocus);

package/dist/src/row.d.ts

@@ -86,7 +86,9 @@ export interface AppFile {
 /**
  * files field → the attached files with their presigned `url` (empty if none).
  * Skips entries the server didn't presign (no `url`) so a consumer never renders
- * an unservable file. Map to `@lotics/ui` `DisplayFile` for FileThumbnail/Gallery.
+ * an unservable file. Pass one to `toDisplayFile` from `@lotics/ui/file_thumbnail`
+ * for FileThumbnail/Gallery — the kit owns that conversion, so don't re-declare
+ * it per app.
  */
 export declare function readFiles(v: unknown): AppFile[];
 /**

package/dist/src/row.js

@@ -113,7 +113,9 @@ export function readLinks(v) {
 /**
  * files field → the attached files with their presigned `url` (empty if none).
  * Skips entries the server didn't presign (no `url`) so a consumer never renders
- * an unservable file. Map to `@lotics/ui` `DisplayFile` for FileThumbnail/Gallery.
+ * an unservable file. Pass one to `toDisplayFile` from `@lotics/ui/file_thumbnail`
+ * for FileThumbnail/Gallery — the kit owns that conversion, so don't re-declare
+ * it per app.
  */
 export function readFiles(v) {
     if (!Array.isArray(v))

package/docs/data_fetching.md

@@ -136,8 +136,11 @@ server validates system conditions by `type` and never reads `field_key` on them
   are no rows yet. It stays `false` during background revalidation of a key that already has rows,
   so consumers never blank loaded data to a spinner on refetch. A key *change* (new params, sort,
   filter, or page) is a fresh load: `loading` goes `true` again unless that key is already cached —
-  `usePaginatedQuery` keeps the previous page's rows on screen during it, which is why skeletons
-  gate on `loading && rows.length === 0`, never `loading` alone. **`isValidating`** is `true`
+  but the previous key's rows STAY on screen while it resolves, for every query, so `rows` never
+  empties mid-flight. That is why skeletons gate on `loading && rows.length === 0`, never `loading`
+  alone: a filter derived from what is on screen re-keys on every keystroke, and gating on
+  `loading` swaps the list for a spinner each time — which unmounts everything the rows contained,
+  images included. **`isValidating`** is `true`
   whenever any request is in flight — use it for a subtle refresh indicator.
 - **`error`** is a `string | null`. A failed query surfaces immediately — there is **no automatic
   retry** (no retry loop that masks the error). The last successful rows for the same key stay

package/docs/workflows.md

@@ -688,6 +688,11 @@ to let the call site supply the type. Keep the loop for FINDING values and put t
   a filtered `query_records` that scans for the row you just made: the filtered form is both an
   extra scan and wrong under concurrency, since a row created between your write and your read
   matches the same filter.
+- **A write that makes rows live can be refused by the plan's record allowance.** `create_records`,
+  a draft submit and a restore all count against the organization's live rows; the one that would
+  exceed the allowance fails the run with a sentence for a person ("Your plan's record allowance is
+  full…", in the reader's language) and none of that call's rows land. Archiving records frees
+  room. Updates never trip it.
 
 ### Keep expensive steps off the path the caller waits on
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/app-sdk",
-  "version": "0.87.5",
+  "version": "0.87.7",
   "description": "Runtime SDK for Lotics custom-code apps \u2014 typed hooks, postMessage bridge, mount entry point",
   "type": "module",
   "exports": {