@jsenv/navi 0.30.22 → 0.30.24

package/docs/actions.md

@@ -554,8 +554,8 @@ const SUMMARY = createAction(fetchSummary, {
 });
 ```
 
-After a listed write, its instances that answered, or are still asking, ask
-again; `on` is read as a resource's is
+After a listed write, its instances that answered, are still asking, or failed
+ask again; `on` is read as a resource's is
 ([resource.md](./resource.md#dependencies-rerun-after-another-resource-writes)).
 
 What the server moves on its own — an email that may bounce, an account being

package/docs/list_refresh.md

@@ -236,6 +236,14 @@ changes what re-reads the slices and nothing else — `GET_MANY` still reruns af
 `POST`. `false` turns a key off. A `withParams()` scope or a relation reads its
 own `rerunOn` the same way, against the resource it is declared on.
 
+A write asks again every read that answered, is still out, or failed. A failed
+read has nothing else to bring it back: left out, one bad answer during a deploy
+would keep a count on its old value until the page reloads. The status does not
+matter, since a write can change what a `403` or a `404` answers, so a read that
+keeps failing costs one request and one error per write, and never a retry loop.
+Two reads stay out: an aborted or never-run one, which nobody is waiting for,
+and a head start that failed, which the screen arriving asks for itself.
+
 Adding `PUT`/`PATCH` to `GET_MANY` is the usual over-correction: it costs a
 request and a `loading` pass to obtain something the response already contained.
 When a `PATCH` "doesn't show", the fix is almost always server-side — return the

package/docs/resource.md

@@ -708,7 +708,7 @@ another collection, drawn from its first item
 
 A resource reruns its own reads after its own writes (`rerunOn`, see
 [list_refresh.md](./list_refresh.md#rerunon-verb-by-verb)), and it does so for
-every read of the resource: a `POST` reruns every `GET_MANY` that completed,
+every read of the resource: a `POST` reruns every `GET_MANY` already asked,
 whatever params each one was bound to. Right for one collection, wrong for a
 resource read under several fixed questions at once — the admins and the guests
 of one `USER`, each list on its own screen. A guest created should not send the
@@ -767,8 +767,9 @@ const ROLE_WITH_OWNERS = ROLE.withParams(
 ```
 
 Any write on a listed resource (`POST`, `PUT`, `PATCH`, `DELETE`) reruns the
-completed `GET` and `GET_MANY` of the resource that declared it, and invalidates
-its `GET_RANGE` readers: its own `rerunOn` is about its own writes. A
+`GET` and `GET_MANY` of the resource that declared it, those that failed included
+([which ones](./list_refresh.md#rerunon-verb-by-verb)), and invalidates its
+`GET_RANGE` readers: its own `rerunOn` is about its own writes. A
 dependency is a facade: `DATABASE` and `DATABASE.withParams(…)` are two of them,
 and only writes on the one listed count. Nothing goes the other way, and nothing
 is inferred — a relation that really is a sub-route of the parent is modelled

package/package.json

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