@jsenv/navi 0.30.10 → 0.30.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/dev/jsenv_navi.js +69 -8
- package/dist/dev/jsenv_navi.js.map +6 -6
- package/dist/jsenv_navi.js +68 -8
- package/dist/jsenv_navi.js.map +6 -6
- package/docs/actions.md +8 -2
- package/package.json +1 -1
package/docs/actions.md
CHANGED
|
@@ -197,6 +197,9 @@ back may find it or ask again, and neither is something to build on.
|
|
|
197
197
|
good for `ms` from the moment it landed, and the first screen asking for those
|
|
198
198
|
params after that asks again: a read worth asking at each visit — a
|
|
199
199
|
measurement, a quota — declares a short one.
|
|
200
|
+
A resource's reads declare it on the resource,
|
|
201
|
+
`resource(name, { keep: { GET: { ms } } })`; left out, coming back asks again,
|
|
202
|
+
while the store draws the row it already holds.
|
|
200
203
|
|
|
201
204
|
### The in-between states of a gesture are real params
|
|
202
205
|
|
|
@@ -277,8 +280,9 @@ at best, a gesture late in a popup. It is for a parameter chosen inside the
|
|
|
277
280
|
component and dying with it. Outside a component,
|
|
278
281
|
`actionRunEffect(action, () => …)` is that same run declared once — it runs on
|
|
279
282
|
the first truthy params, reruns when they change (unless the action declared
|
|
280
|
-
`keep` and still holds the answer for the new ones
|
|
281
|
-
|
|
283
|
+
`keep` and still holds the answer for the new ones, or only a prerun asked for
|
|
284
|
+
them: that answer was read ahead for this arrival and is taken as it is), aborts
|
|
285
|
+
when they go false — and the machinery `routeAction` is built on.
|
|
282
286
|
|
|
283
287
|
**Which of the two it is, is decided by the parameter, not by what draws it.**
|
|
284
288
|
If the parameter is in the address — a path param, a search param bound to a
|
|
@@ -311,6 +315,8 @@ It needs no `<Loading>`, and its failure reaches no boundary: nothing on screen
|
|
|
311
315
|
asked for a prerun, so the owner's `{ run: true }` asks again, once, when it
|
|
312
316
|
reads it. A failure of the owner's own run is shown, and asked again by a
|
|
313
317
|
`rerun()`, never by a render. A head start still running is the owner's wait.
|
|
318
|
+
A write that would ask a read again drops a head start instead: the owner
|
|
319
|
+
finds it idle and asks for itself.
|
|
314
320
|
|
|
315
321
|
`{ onLoad }` is what the screen does with the data **once, when it becomes
|
|
316
322
|
known** — seed the fields someone is about to edit, focus something, remember
|