@jsenv/navi 0.29.227 → 0.29.228
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 +36 -8
- package/dist/dev/jsenv_navi.js.map +3 -3
- package/dist/jsenv_navi.js +36 -8
- package/dist/jsenv_navi.js.map +3 -3
- package/docs/data_states.md +7 -0
- package/package.json +1 -1
package/docs/data_states.md
CHANGED
|
@@ -73,6 +73,13 @@ means something different:
|
|
|
73
73
|
|
|
74
74
|
Two consequences worth stating out loud.
|
|
75
75
|
|
|
76
|
+
**A first load is only a first load when nothing is known.** A resource `GET`
|
|
77
|
+
whose params name a row the store already holds — read earlier by a `GET_MANY`,
|
|
78
|
+
a relation, a list — starts on the second line, not the first: the row is drawn
|
|
79
|
+
and the request goes out behind it. The response replaces it, and a failure
|
|
80
|
+
lands beside it like any refresh failure. A `GET` of a row the store lacks
|
|
81
|
+
still starts on the first line, so what is drawn is never a different row.
|
|
82
|
+
|
|
76
83
|
**The emptiness test is `data === undefined`, never `loading`.** Reading
|
|
77
84
|
`loading` as "there is nothing to display" blanks the screen on every refresh —
|
|
78
85
|
for a checkbox ticked on one row of a list, the whole list goes.
|