@lotics/app-sdk 0.98.1 → 0.98.3

package/dist/src/hooks.d.ts

@@ -343,8 +343,11 @@ export interface WorkflowResult<TData = unknown> {
      * Either half of the round trip fills it: the SERVER, when the payload does
      * not match what the alias declares, and the workflow's own
      * `return({ field_errors })`. One key, so a screen wires the control once
-     * rather than branching on which half refused. Absent when neither named a
-     * field — and an older server names none.
+     * rather than branching on which half refused. A step whose write the
+     * target table refuses (its `before_*` workflow, a unique tuple) keys its
+     * sentence by the FIELD key (`fld_…`) instead, since the table has never
+     * heard of the input. Absent when nothing named a field — and an older
+     * server names none.
      */
     field_errors?: Record<string, string>;
 }

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.1",
+  "version": "0.98.3",
   "description": "Runtime SDK for Lotics custom-code apps \u2014 typed hooks, postMessage bridge, mount entry point",
   "type": "module",
   "exports": {