Remote / API
foldkit-remote/why
foldkit-remote/why: development tools that say why a read shows what it
shows — every fact the Model holds about what the read reads, by typed
reference rather than by the store's marks (#248) — and what a query read
is. An entry of its own, so a page that never explains a read keeps none of
it (#378).
Functions
explain | What a query read is and what it currently is, as one serializable value — data-query-DESIGN §29.1: the domain, the definition and its input, the connection… |
timeline | Each change of each read's tag across a recorded history (the Messages update handled, each with the Model it left, as Foldkit's devtools records them),… |
why | Why a read shows what it shows. Any Remote read: Data.get, live or Data.query, or a projection made of them. |
Values
ReadWhy | Why a read shows what it shows. because is every fact the Model holds about what it reads, the reason that decides state first; message is that reason in… |
ShownBy | What shows something the server has not said: a write, an overlay, or a live event. |
Why | One fact about a read. ReadWhy.because lists every one the Model holds. |
WhyTerm | One where predicate of a list's body, judged over the row as the client placed it. Null is SQL's unknown, which keeps a row out; Unknown rests on what the… |
Interfaces
ExplainedDependencies | A query body's Dependencies as plain data: each field by its Entity's name and key. |
ExplainOptions | The active record a read is explained against: the one subscriptions takes. |
QueryExplanation | What one query read is, and what it currently is — data-query-DESIGN §29.1. |
ReadStep | One change of a read's tag in a history, with the Message that made it. |