@jsenv/navi 0.29.90 → 0.29.92

package/docs/AI_INSTRUCTIONS.md

@@ -144,6 +144,15 @@ consistency across the app, not from any single call site.
   `signal` carrying something is an answer). Read it before a screen that
   modifies an existing resource (`pristineKey`), and before reaching for
   `canSendWhileUnchanged` because a submit "does nothing".
+- `distributeChildStates` on a group — the way down asked once for ALL the
+  children, when they cannot be placed one at a time (four seats where who sits
+  down decides who moves). The mirror of `aggregateChildStates`; see
+  control_object.md. Read it before writing a `uiAction` whose only job is to
+  translate. Two neighbouring questions have answers already: a yes/no shown as
+  two rows needs no translation (`List.Item value={true}` beside
+  `value={false}` IS a boolean control), and a cross that means "back to the
+  usual answer" needs none either — clearing empties, and `placeholder` is
+  where that sentence is written (control_value.md).
 - `docs/control_object.md` — a value made of several controls: `<ControlGroup>`
   (the shape) vs `<Form>` (the shape plus a send), what a group's `name` does
   and what a nameless one merges, and what a `<Picker type="object">` needs in
@@ -162,7 +171,11 @@ consistency across the app, not from any single call site.
   the bounds of a span PUSH each other while they turn (`minDuration`) instead
   of being refused at send, and `placeholder` is a position shown without being
   an answer — for a span that is optional ("any time of day") on wheels that
-  have no blank row to land on. Read this before writing a time input, and
+  have no blank row to land on. A clear (or a value written as `undefined`) puts
+  such a pair back on its placeholder and back to answering nothing, so a row's
+  cross means what it says. `hours` bounds what the wheels offer
+  (`{ min: 7, max: 21 }`, or the list itself) — rows nobody can land on are rows
+  in the way. Read this before writing a time input, and
   before making a pair of wheels say "nothing set" by hand.
 - `docs/control_group.md` — `<Group>`: several controls reading as one framed
   object (one border per seam, radius on the outer corners only). Read it

package/docs/actions.md

@@ -72,6 +72,16 @@ const userAction = getUser.bindParams({ id: userIdSignal });
 | `reset()`  | Aborts what is running and puts the action back to idle, data and all.   |
 | `abort()`  | Calls off the run in flight, keeping the data it had.                    |
 
+### Aborting saves resources, it does not undo
+
+`abort()` cancels what can still be cancelled — a `fetch` wired to the
+callback's `signal` — and nothing more. The server may have done the work
+before the cancellation reached it, or may not honor cancellations at all:
+whether the work happened is known from the run's settlement alone. For that
+reason a run's promise settles only when its callback settles, even after an
+abort, and anything sequenced behind a run — an optimistic control's queued
+request, for instance — waits for that settlement, never for the abort.
+
 ## Reading an action
 
 ```jsx
@@ -175,12 +185,12 @@ the event that caused it, and `findEvent(event, type)` walks that chain back:
   clearable
   uiAction={(value, event) => {
     if (findEvent(event, "navi_clear_ui_state")) {
-      // the clear cross was pressed — for this row that means "back to the
-      // profile level", not "empty"
-      draft.level = profile.level;
+      // the cross was pressed — the row is empty because somebody emptied it,
+      // not because the last player left the list
+      askAgainLater();
       return;
     }
-    draft.level = value;
+    draft.players = value;
   }}
 />
 ```

package/docs/control_object.md

@@ -152,6 +152,18 @@ are not all there yet:
   group holds. Only a child controlled by a `value`/`checked` prop is left
   alone: its owner decides.
 
+`distributeChildUIState` is asked child by child, which is fine while each child
+can be placed on its own. When it cannot — four seats where who sits down
+decides who moves, a row whose first answer changes what the others may show —
+`distributeChildStates` is the same way down asked ONCE for all of them:
+
+```js
+distributeChildStates: (groupValue, children) => new Map([[child, state], …])
+```
+
+the mirror of `aggregateChildStates`, which already sees every child. A child
+the Map does not name is left where it is. Given both, the plural one wins.
+
 A group with an `aggregateChildStates` of its own is outside all of this: what
 it returns is taken as the truth, `undefined` included. That is the one way such
 a group says **"I have nothing to say yet"** — return `undefined` while the

package/docs/control_value.md

@@ -10,6 +10,9 @@ somewhere else in the app.
 - [What a signal holds, control by control](#what-a-signal-holds-control-by-control)
 - [Empty keeps the shape of the question](#empty-keeps-the-shape-of-the-question)
 - [Which controls take a `signal`](#which-controls-take-a-signal)
+- [The PROP is what controls, not its value](#the-prop-is-what-controls-not-its-value)
+- [A yes/no shown as two rows](#a-yesno-shown-as-two-rows)
+- [Clearing, resetting, and what is shown meanwhile](#clearing-resetting-and-what-is-shown-meanwhile)
 - [`value` and `signal` exclude each other](#value-and-signal-exclude-each-other)
 - [A `stateSignal` brings more than a value](#a-statesignal-brings-more-than-a-value)
 
@@ -160,6 +163,76 @@ own `selected` — but not expect the two to arbitrate. An item that declares
 it. On screen that reads as a list where clicking does nothing, so navi says it
 in dev the moment the two claims meet: bind one end or the other, not both.
 
+## The PROP is what controls, not its value
+
+`value` (and `checked`, and a row's `selected`) makes a control controlled by
+being **there**. Its value is a separate question: `value={undefined}` says "I
+hold this one, and right now it holds nothing" — the control shows nothing, and
+nothing else can fill it. That is a real state and it is the one asked for.
+
+The trap is the shorthand for an optional prop:
+
+```jsx
+// WRONG — the key is always there, so the control is always controlled,
+// and the group above it can never fill it
+<Input checked={bound ? undefined : checked} />
+
+// RIGHT — the prop is there only when you are the one answering
+<Input {...(bound ? {} : { checked })} />
+```
+
+Passing a prop the code knows will always be `undefined` is the same mistake
+written once instead of twice: leave it out. navi says so in dev when a group
+tries to place a child that has claimed itself this way.
+
+## A yes/no shown as two rows
+
+A checkbox is one way to ask a yes/no; two rows one can compare — "Publique, we
+propose it to players looking for this kind of game" against "Privée, it travels
+only by the link you send" — is another, and it is the same value:
+
+```jsx
+<Picker name="visibility" signal={isPublicSignal}>
+  <List selectable>
+    <List.Item value={true}>Publique …</List.Item>
+    <List.Item value={false}>Privée …</List.Item>
+  </List>
+</Picker>
+```
+
+Nothing translates: the row holds the boolean, the form carries the boolean.
+What cannot be done is give a row `undefined` to mean "no value" — `undefined`
+is what UNCHECKED means, here as in HTML, so such a row can never be ticked.
+A value the control can hold is a value one can see; "nothing chosen" is the
+absence of a row, not a row.
+
+## Clearing, resetting, and what is shown meanwhile
+
+Three things that look alike and are not:
+
+| gesture / prop            | what it does                                                                        |
+| ------------------------- | ----------------------------------------------------------------------------------- |
+| `--navi-clear`, the cross | the control holds its own empty — `""`, `[]`, `{}`, unchecked                       |
+| `--navi-reset`            | the control goes back to its `defaultValue`                                         |
+| `defaultValue`            | where it starts, and where a reset goes back to — a real value, sent like any other |
+| `placeholder`             | what is SHOWN while it holds nothing, and never a value                             |
+
+So a row whose cross means "back to the one from my profile" needs nothing of
+its own: clearing empties it, and `placeholder` is where that sentence is
+written.
+
+```jsx
+<Picker clearable placeholder="Celui de mon profil" signal={sideSignal} />
+```
+
+What the app then reads is `undefined` (or the empty of the row's type), which
+is what "nothing chosen here, use the usual answer" already means everywhere
+else — the same rule as an emptied signal falling back on its default.
+
+A control that cannot show emptiness — a pair of wheels has no blank row to land
+on — takes the same `placeholder` as a POSITION instead of a word (see
+`TimeWheel`): shown, and still not an answer.
+
 ## `value` and `signal` exclude each other
 
 `value` (or `checked`) says "you hold it", `signal` says "the signal holds it".

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/navi",
-  "version": "0.29.90",
+  "version": "0.29.92",
   "type": "module",
   "description": "Library of components including navigation to create frontend applications",
   "repository": {