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

package/README.md

@@ -173,8 +173,10 @@ state. `open` drills into the row.
 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` takes the command's name and opens its form with the
-picked ids already in place.
+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.3",
+  "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": "d2a7156f66c7f5f42837c6d5c13faf6d33a6df7e"
+  "gitHead": "d65285daddaf66f75ff759d31596a0aee84cd3cb"
 }

package/src/ReventlessSlots.res

@@ -21,7 +21,7 @@ type viewPayload = {
   total?: int,
   selection?: array<string>,
   picked?: array<rowPayload>,
-  run?: string => unit,
+  run?: unit => unit,
 }
 
 type hyperscript

package/src/ReventlessSlots.resi

@@ -57,8 +57,13 @@ type viewPayload = {
       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, by name. */
-  run?: string => unit,
+  /** 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. */

package/src/index.d.ts

@@ -63,8 +63,13 @@ export interface ViewPayload<Row = Record<string, unknown>> {
    *  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, by name. */
-  run?: (command: string) => void
+  /** 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