@reventlessdev/reventless-ui-slots 3.0.0-alpha.2 → 3.0.0-alpha.4

package/README.md

@@ -145,6 +145,11 @@ the question.
 | `tracker.summary` | row | the line beside one row's name; its summary fields |
 | `detail.media` | row | the media column of a `detailLayout: "media"` page; the record's picture |
 | `detail.aside` | row | above the field set on a `detailLayout: "media"` page; nothing by default |
+| `list.selection` | view | the bar over a list whose rows the caller can pick out: what is picked, a way to empty it, and the one command that takes the lot |
+
+`list.selection` is the one id that is not `<mode>.<region>`: it belongs to the
+list itself rather than to a mode, which is what lets a picking made in the table
+survive a switch to cards.
 
 An id nothing offers is reported to the console at boot — a renderer nothing will
 ever call is a mistake the running app would otherwise never mention.
@@ -156,7 +161,7 @@ ever call is a mistake the running app would otherwise never mention.
 { row, label?, image?, open?, actions? }
 
 // view slot
-{ rows, total?, selection?, run? }
+{ rows, total?, selection?, picked?, run? }
 ```
 
 `row` is the read model's own JSON. `image` is already resolved for this
@@ -164,10 +169,14 @@ deployment's asset origins. `actions` are already resolved against the
 deployment's declarations, the caller's permissions and the row's lifecycle
 state. `open` drills into the row.
 
-`selection` and `run` are declared and filled by nothing yet — cross-row
-selection is its own piece of work. They are in the contract from the start
-because discovering that a region needs a second arity after publishing would be
-a breaking change.
+`selection` is the picked row **ids**; `picked` is the rows behind them, each as
+the same row-slot payload above. Both, and not just the ids, because a list's
+window is replaced page by page: a row picked on page 1 is gone from `rows` by
+the time the caller is on page 3, and a bar whose job is to name what is in it
+cannot look one up. `run` opens the command's form with the picked ids already in
+place, and takes nothing: the region has exactly one command, settled before the
+payload was built, so a renderer naming it would be repeating a decision it
+cannot check.
 
 ## What a slot may not do
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reventlessdev/reventless-ui-slots",
-  "version": "3.0.0-alpha.2",
+  "version": "3.0.0-alpha.4",
   "description": "Types and one runtime helper for writing custom renderers into the regions of Reventless AutoUI's standard view modes.",
   "license": "Apache-2.0",
   "type": "module",
@@ -54,5 +54,5 @@
     "react-dom": "^18.3.1",
     "rescript": "^12.3.0"
   },
-  "gitHead": "6d74b362ba047678919b27c22f84e698dea48741"
+  "gitHead": "d65285daddaf66f75ff759d31596a0aee84cd3cb"
 }

package/src/ReventlessSlots.res

@@ -20,7 +20,8 @@ type viewPayload = {
   rows: array<JSON.t>,
   total?: int,
   selection?: array<string>,
-  run?: string => unit,
+  picked?: array<rowPayload>,
+  run?: unit => unit,
 }
 
 type hyperscript
@@ -144,6 +145,19 @@ module Format = {
     let at = Date.fromString(iso)
     Float.isNaN(Date.getTime(at)) ? "" : Date.toLocaleDateString(at)
   }
+
+  let pad = (n: int): string => n < 10 ? "0" ++ Int.toString(n) : Int.toString(n)
+
+  let isoDay = (iso: string): string => {
+    let at = Date.fromString(iso)
+    Float.isNaN(Date.getTime(at))
+      ? ""
+      : Int.toString(Date.getFullYear(at)) ++
+        "-" ++
+        pad(Date.getMonth(at) + 1) ++
+        "-" ++
+        pad(Date.getDate(at))
+  }
 }
 
 let titleOf = (payload: rowPayload): string =>
@@ -208,5 +222,6 @@ module RowSlot = {
 module ViewSlot = {
   let cardsEmpty = "cards.empty"
   let galleryEmpty = "gallery.empty"
-  let all = [cardsEmpty, galleryEmpty]
+  let listSelection = "list.selection"
+  let all = [cardsEmpty, galleryEmpty, listSelection]
 }

package/src/ReventlessSlots.res.mjs

@@ -121,10 +121,22 @@ function day(iso) {
   }
 }
 
-let Format = {
-  money: money$1,
-  day: day
-};
+function pad(n) {
+  if (n < 10) {
+    return "0" + n.toString();
+  } else {
+    return n.toString();
+  }
+}
+
+function isoDay(iso) {
+  let at = new Date(iso);
+  if (Number.isNaN(at.getTime())) {
+    return "";
+  } else {
+    return at.getFullYear().toString() + "-" + pad(at.getMonth() + 1 | 0) + "-" + pad(at.getDate());
+  }
+}
 
 function titleOf(payload) {
   let label = payload.label;
@@ -189,17 +201,27 @@ let cardsEmpty = "cards.empty";
 
 let galleryEmpty = "gallery.empty";
 
+let listSelection = "list.selection";
+
 let all$1 = [
   cardsEmpty,
-  galleryEmpty
+  galleryEmpty,
+  listSelection
 ];
 
 let ViewSlot = {
   cardsEmpty: cardsEmpty,
   galleryEmpty: galleryEmpty,
+  listSelection: listSelection,
   all: all$1
 };
 
+let Format = {
+  money: money$1,
+  day: day,
+  isoDay: isoDay
+};
+
 export {
   h,
   RowSlot,

package/src/ReventlessSlots.resi

@@ -42,19 +42,28 @@ type rowPayload = {
   actions?: array<action>,
 }
 
-/** What a per-view region is handed. `selection` and `run` are declared and
-    filled by nothing yet — cross-row selection is its own piece of work. They
-    are in the contract from the start because discovering that a region needs a
-    second arity after publishing would be a breaking change. */
+/** What a per-view region is handed. */
 type viewPayload = {
   /** The rows the mode is currently drawing — its page window, not the table. */
   rows: array<JSON.t>,
   /** How many rows that window holds. */
   total?: int,
-  /** Row ids the caller has picked out, where the mode offers picking. */
+  /** Row ids the caller has picked out, where the view offers picking. */
   selection?: array<string>,
-  /** Start the region's one command, by name. */
-  run?: string => unit,
+  /** The rows behind `selection`, as they were when picked.
+
+      A list's window is replaced page by page, so a row picked on page 1 is
+      gone from `rows` by the time the caller is on page 3 — and a bar whose job
+      is to name what is in it cannot look one up. So the rows travel, each as
+      the same `rowPayload` a per-row region is handed. */
+  picked?: array<rowPayload>,
+  /** Start the region's one command, with the picked rows already in it.
+
+      Takes nothing. A region has exactly one command by construction, and which
+      one it is was settled before this payload was built — naming it here would
+      be a second copy of a decision made once, and a renderer has no honest way
+      to know the name it would be passing. */
+  run?: unit => unit,
 }
 
 /** React's `createElement`, as the shell handed it over. */
@@ -187,8 +196,21 @@ module Format: {
       most currencies and quietly wrong for JPY and TND. */
   let money: ((float, string)) => string
 
-  /** An ISO instant as a short local date. `""` when it does not parse. */
+  /** An ISO instant as a short date **in the viewer's own locale**.
+
+      Which format that is comes from the runtime, not from you or from the
+      deployment: the same order reads `9/4/2026` to one customer and `04/09/2026`
+      to another, and a screenshot never matches CI. That is right for a surface
+      whose readers are the public, and wrong wherever a date has to be
+      unambiguous or stable — take `isoDay` there. */
   let day: string => string
+
+  /** An ISO instant as `YYYY-MM-DD`, the same everywhere.
+
+      Built from the **local** calendar parts rather than by slicing the string,
+      which would silently publish the UTC date and land a day out either side of
+      midnight for most of the world. */
+  let isoDay: string => string
 }
 
 /** What the mode would have titled this row, else the row's own `name`.
@@ -216,5 +238,13 @@ module ViewSlot: {
   let cardsEmpty: string
   /** The tile grid when the view has no rows. */
   let galleryEmpty: string
+  /** The bar over a list whose rows the caller can pick out: what is picked, a
+      way to empty it, and the one command that takes the lot.
+
+      Offered by the list producer rather than by a view mode — the first id
+      that is not `<mode>.<region>`. The list renders the mode inside its own
+      chrome and the bar is that chrome, so a picking made in the table survives
+      a switch to cards and the bar has to outlive both. */
+  let listSelection: string
   let all: array<string>
 }

package/src/index.d.ts

@@ -48,21 +48,28 @@ export interface RowPayload<Row = Record<string, unknown>> {
   actions?: SlotAction[]
 }
 
-/** What a per-view region is handed.
- *
- *  `selection` and `run` are declared and filled by nothing yet: cross-row
- *  selection is its own piece of work. They are here from the start because
- *  discovering that a region needs a second arity after the contract is
- *  published would be a breaking change. */
+/** What a per-view region is handed. */
 export interface ViewPayload<Row = Record<string, unknown>> {
   /** The rows the mode is currently drawing — its page window, not the table. */
   rows: Row[]
   /** How many rows that window holds. */
   total?: number
-  /** Row ids the caller has picked out, where the mode offers picking. */
+  /** Row ids the caller has picked out, where the view offers picking. */
   selection?: string[]
-  /** Start the region's one command, by name. */
-  run?: (command: string) => void
+  /** The rows behind `selection`, as they were when picked.
+   *
+   *  A list's window is replaced page by page, so a row picked on page 1 is gone
+   *  from `rows` by the time the caller is on page 3 — and a bar whose job is to
+   *  name what is in it cannot look one up. So the rows travel, each as the same
+   *  `RowPayload` a per-row region is handed. */
+  picked?: RowPayload<Row>[]
+  /** Start the region's one command, with the picked rows already in it.
+   *
+   *  Takes nothing. A region has exactly one command by construction, and which
+   *  one it is was settled before this payload was built — naming it here would
+   *  be a second copy of a decision made once, and a renderer has no honest way
+   *  to know the name it would be passing. */
+  run?: () => void
 }
 
 /** Anything React will render. Deliberately structural — the package declares no
@@ -126,8 +133,14 @@ export type RowSlotId =
  * | --- | --- |
  * | `cards.empty` | the card grid when the view has no rows |
  * | `gallery.empty` | the tile grid when the view has no rows |
+ * | `list.selection` | the bar over a list whose rows the caller can pick out |
+ *
+ * `list.selection` is the one id that is not `<mode>.<region>`: it belongs to
+ * the list producer, not to a mode. The list renders the mode inside its own
+ * chrome and the bar is that chrome, so a picking made in the table survives a
+ * switch to cards and the bar has to outlive both.
  */
-export type ViewSlotId = 'cards.empty' | 'gallery.empty'
+export type ViewSlotId = 'cards.empty' | 'gallery.empty' | 'list.selection'
 
 /**
  * Identity helper: type-checks a `register` function without changing it.