@lotics/app-sdk 0.112.0 → 0.113.0

package/dist/index.js

@@ -25542,6 +25542,9 @@ var queryGroupNodeSchema = zod_default.object({
   by: zod_default.array(queryGroupKeySchema).describe(
     "Group keys: input column names, or `{ bucket: { source, granularity, output } }` date buckets. A bucket truncates a date/datetime column to the bucket START as a `date` column (wall-clock semantics; `week` starts on ISO Monday; null source \u2192 null bucket). Empty = single-row aggregate."
   ),
+  sets: zod_default.array(zod_default.array(zod_default.string())).min(1).optional().describe(
+    "Several groupings answered by one read: each lists the `by` outputs it groups by (`[]` = one row over every row). A key outside a row's set is null there, and `__grouping` holds the set's bits: one per `by` key it leaves out, the last key the lowest. Absent: one grouping by every key."
+  ),
   aggregates: zod_default.array(queryAggregateColumnSchema).min(1)
 });
 var queryWindowNodeSchema = zod_default.object({

package/docs/queries.md

@@ -279,6 +279,11 @@ Full semantics in §8. `by` may be empty (a single-row aggregate); `aggregates`
 Aggregate operation × input-column type is validated at bind. Grouping collapses rows —
 addressing is `null`. An aggregate's `filter` limits it to the rows that match (§8).
 
+`sets` answers several groupings in one read: `"sets": [["status", "period"], ["status"], []]`
+groups by both keys, by `status` alone, and over every row, in one pass. A key a set leaves out
+is `null` on its rows, and `__grouping` names each row's set — a bit per `by` key it leaves out,
+the last key the lowest bit (`["status"]` above is `1`, `[]` is `3`).
+
 ### `window` — aggregate without collapsing
 
 ```jsonc

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/app-sdk",
-  "version": "0.112.0",
+  "version": "0.113.0",
   "description": "The SDK a Lotics custom-code app reads and writes through \u2014 typed hooks over the host bridge, cell readers, mount() and AppRouter",
   "type": "module",
   "exports": {