@lotics/app-sdk 0.98.2 → 0.98.4

package/dist/src/hooks.js

@@ -227,8 +227,9 @@ export function useInfiniteQuery(alias, params, opts) {
     // Keyset (seek) pagination: each page seeks past the previous page's
     // `next_cursor` instead of an increasing OFFSET, so deep scrolls stay O(page)
     // and never skip/duplicate a row as the set shifts. The cursor is opaque; the
-    // server keysets a sortable key (or the id default) and falls back to offset
-    // transparently. `loadMore`/`rows` are unchanged — the cursor is internal.
+    // server keysets a sortable key (the query's own order when `sort` is unset,
+    // else the id) and falls back to offset transparently. `loadMore`/`rows` are
+    // unchanged — the cursor is internal.
     const getKey = (index, prev) => {
         if (mockRows || !enabled)
             return null;

package/docs/data_fetching.md

@@ -241,8 +241,9 @@ Reads paginate two different ways, and the difference is load-bearing:
   opaque cursor instead of counting an offset, so a deep scroll stays O(page) and — the reason it
   matters — **never skips or duplicates a row as the set shifts** under concurrent inserts/deletes.
   The cursor is internal: the hook sends it and reads the next one back; you never see it. The
-  server keysets a single sortable key (the runtime `sort`, or the record-id default) and falls
-  back to offset transparently for a multi-key sort it can't seek. So an infinite feed needs **no
+  server keysets a single sortable key (the runtime `sort`, else the template's own order on a
+  column it projects, else the record id) and falls back to offset transparently for a multi-key
+  sort it can't seek. So an infinite feed needs **no
   dedupe** — key rows by `__source_record_id` for stable React keys, not to guard against repeats.
 - **`useQuery`, `usePaginatedQuery`, and manual `rpc("query", { limit, offset })` use offset
   pagination** — count `offset` rows, skip them, return the next page. Two consequences a keyset

package/docs/queries.md

@@ -570,7 +570,9 @@ tokens fail deploy.
 axes from ONE named query — don't shard into a query-per-combination. Mark each scoping param
 `required: false`; the server **prunes every filter condition (or traversal) whose
 `{{params.x}}` the caller didn't pass** — then collapses emptied groups — so an unset axis
-stops constraining instead of erroring. No-op for all-required queries.
+stops constraining instead of erroring. A param passed empty (`""`, `[]`, `null`) counts as not
+passed. A REQUIRED param passed empty is refused (400, naming the condition it feeds) when a
+filter reads it.
 
 ```jsonc
 "search": {

package/package.json

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