Skip to main content

Module fork

laser_wire

Module fork 

Source

Structs§

ForkCreate
Wire form of the AGDX_FORK_CREATE request. Wire-stability-bound, built through the SDK’s fork handle in application code.
ForkDelete
Wire form of the AGDX_FORK_DELETE (squash) request.
ForkInfo
A fork’s metadata, returned by create and list.
ForkList
Wire form of the AGDX_FORK_LIST request.
ForkPromote
Wire form of the AGDX_FORK_PROMOTE request.
ForkPut
Wire form of the AGDX_FORK_PUT request. Wire-stability-bound, built through the SDK’s fork handle in application code.

Enums§

ForkError
Why a fork operation failed.
ForkKind
How a fork relates to the trunk it branched from.
ForkOutcome
The successful outcome of a fork command, shaped per op.
ForkReply
The result of a fork op: Ok with the outcome, or Err with a failure.
ForkStatus
Lifecycle of a fork.

Functions§

validate_fork_id
The canonical fork-id safelist, shared by every fork-serving backend. A fork id is caller-chosen and a backend that overlays a fork inlines it into a copy-on-write query as a quoted identifier, so the charset must be a strict safelist, not just a length bound: this is the one anti-injection rule. A valid id is non-empty, at most MAX_FORK_ID_BYTES bytes, and made only of ASCII letters, digits, -, _, and .. A backend that binds the id as a parameter may skip the call, but one that inlines it gets the defense for free by calling this before use.