Optional Readonly~topThe data fields the handle also shows on its top level: the screen's one
main identifier (identity), or none. A type only, never set.
ReadonlyactionThe edges the definition carries for itself and its handle does not show: each is taken from inside an action, after the person's input (“An edge the handle does not show”). The engine binds them so the trail names the step and a retrace takes it again, and the reachability follows their targets; no handle offers one. Empty for a definition whose transitions are all calls.
ReadonlyactionsOptional ReadonlybeforeWhat the engine runs when a transition is about to cover or close the
screen, while its chain and endpoint are still in front: the app's
departure work that goes out before the covering screen's burst. A screen
and a feed declare it (an item does not). It receives the visit in
progress, cannot fail, and runs before the transition and before leave.
Optional ReadonlybeforeWhat the engine runs when a transition is about to bring the screen back on
top (a tab tap back to it, the covering screen's back), while the screen
in front still has its chain and endpoint: the app's tap-time work, the
counterpart of the first show's burst before its own navigation event. Only
a screen declares it. It cannot fail, and runs before the transition and
before resume.
ReadonlydataWhat enter returns: the user's data, under the handle's data; never in a trail.
ReadonlyenterReadonlyidReadonlyinputWhat an edge passes to enter — for an item, the schema of one list entry.
ReadonlykindReadonlyleaveWhat the engine runs each time the thing stops being on top — covered by another screen, closed, or left by a tab switch — after the transition that did it committed. It receives the visit that ended, with its duration by the engine's clock. It cannot fail; absent when the thing does nothing then.
Optional ReadonlymodalWhether the app presents this screen as a bottom sheet over the screen
under it (the app's contained_within_bottom_sheet on its navigation; a
private check holds every declaration to the recordings). Its open and its
close are navigations like any other — the covered screen's leave and
resume run, its chain entry is stamped again — but the sheet does not
pause the screen under it, so that screen's resume receives
resumedFrom.fromBottomSheet: true and does not run what it does on coming back
from being paused. Absent: an ordinary screen, which replaces the one under
it.
Optional ReadonlyreadHow a checkpoint written by an earlier release is read into this screen:
the stored input and data, in the shape that release gave them, become the
current stored shape before the definition's schemas decode them. A field
the release wrote and the screen no longer holds is read with a schema of
its own and mapped into where its fact lives now, or dropped with a logged
StoredSnapshotFieldDropped; it never fails the restore (“Stored snapshots
of earlier releases”). Absent on a screen whose stored shape never changed;
a frame already in the current shape passes through it unchanged.
Optional ReadonlyreadThe same reading for an input stored alone — a trail's root and steps, the process's root: the input of an earlier release, read into the current stored shape before the screen's input schema decodes it.
ReadonlyresumeWhat the engine runs each time the thing is on top again after a leave —
the screen that covered it was closed — after that transition committed.
Never on the first show (that is enter), never after a rolled-back
transition. It cannot fail; absent when the thing does nothing then.
ReadonlystateWhat continuing from it needs, from its input and data (and, for an item, its host screen's state).
What screens and items share: an id, a kind, the schemas, the
enterthe engine runs when the thing is shown, and the actions.