@jsenv/navi 0.29.415 → 0.29.416

package/docs/resource.md

@@ -292,9 +292,13 @@ Keep their **ids**, not the objects: an object is a snapshot, and it stops
 following its row the moment anything writes to it. `RESOURCE.useAllByIds(ids)`
 reads those rows as they are now — a kept id turned back into something that
 stays fresh, and the ids the store no longer holds simply drop out.
-`RESOURCE.useById(id)` is the singular, `RESOURCE.useArray()` the whole store;
-all three subscribe the render that calls them, and none is a hook (a `.map()`
-over them is fine).
+`RESOURCE.useById(id)` is the singular, `RESOURCE.useArray()` the whole store.
+None is a hook (a `.map()` over them is fine), and each subscribes the render
+that calls it to what it returns: `useById` and `useAllByIds` to the rows they
+hand back — a card reading its own row stays still while other rows of the
+store are written, and re-renders when its row is — `useArray` to the whole
+store. An entry of `useAllByIds` given by a unique key rather than by id can
+only be found by reading the whole store, and that read follows it too.
 
 ## Relations: pick one of the four methods
 

package/docs/route_transitions.md

@@ -643,10 +643,13 @@ elements):
   at a route (`<Link route>`, `<Button route>`) reads one flag — whether it is
   current — and stays still unless that flips: a profile opening leaves the
   links to a hundred other profiles exactly as they were (on the list of
-  thirty cards: 90 re-renders gone, first frame 58 → 41 ms). What else reacts
-  is worth keeping to what has to — measured: every card of the page being
-  left re-rendering when the page arriving loads its own games into the store
-  the cards read theirs from.
+  thirty cards: 90 re-renders gone, first frame 58 → 41 ms). A row read with
+  `RESOURCE.useById` follows that row only, so the page arriving loading rows
+  of its own into the same store leaves the cards of the page being left as
+  they were. What reacts is then the page's own reading of its route's action
+  — its params, its data and its state all move as the route stops matching —
+  and that re-renders the page with everything in it (on the list of thirty
+  cards: about 1,150 component renders, the largest share of the callback).
 - **Re-rendering what did not change, on the press itself.** A component that
   only wants a yes or a no reads a computed flag, not the signal it is derived
   from: a list whose rows each read the count of runs in flight re-rendered

package/package.json

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