Skip to main content

Module staging

Module staging 

Source
Expand description

The write pipeline every write tool ends in: find what the call changed, validate written blocks with the CMS, and stage the call, or on a dry run tell what staging it would do.

Re-exportsΒ§

pub use report::WriteReport;

ModulesΒ§

page_writes πŸ”’
Full page snapshots for the pages a call changed, with the exercises that follow their blocks.
report πŸ”’
What a write call reports back: the staging summary and the hints that follow it.
validation πŸ”’
Validating the blocks a call changed with the CMS, and writing back their normalised form.

StructsΒ§

DerivedWrites πŸ”’
What a write call stages, found from its WriteSource.
WriteRequest
One write call for commit.

EnumsΒ§

WriteMode
Whether a write call stages its changes or only tells what staging them would do.
WriteSource
Where a write call’s entity writes come from.

FunctionsΒ§

commit
Runs the pipeline from the user’s staged state to after: validate, find the written entities and stage them as one call, or on a dry run tell what staging them would do. Holds no pooled connection while the validator runs.
derive_writes πŸ”’
live_snapshots πŸ”’
The live state of each written entity the user has no staged changes to, as the call read it. Pages were read twice, as blocks with the view and in full when their snapshots were built; a page that changed in between is a stale read.
staged_state_read πŸ”’
The staged state writes were built on: the changeset rows of the view and the live state of the other entities.
stale_read πŸ”’