Skip to main content

Module fragments

Module fragments 

Source
Expand description

The texts rk depend add serves: one fragment set per manager, and the seed file for a manager the target has no file for.

Every text is an authored file under blocks/, per distribution:a-human-faced-artifact-is-authored-text; each carries RK_DEP_* tokens rendered with a plain replace, never a format, so a ${system} interpolation survives untouched. A fragment describes where it goes in a form a coding agent can apply with no parser: a closed placement vocabulary, a literal anchor substring, and a three-state present from the lexical observation.

Structs§

Anchor
Where a fragment goes.
Fragment
One fragment: what to add, where, and whether it is already there.
Tokens
The values a block’s tokens render to. A token whose value is absent is left in place; the matrix selects no block that needs it.

Constants§

BLOCK_NAMES
Every depend block, by name.

Functions§

block
One authored block, by name; the payload is compiled in, so a missing name is a build defect the tests catch, never a runtime path.
first_found
The first needle the text holds, as the literal a reader can search.
flake_ref
The flake reference for a forge host and path at a tag, where the host has a flake reference type: github: and gitlab:.
fragment
One rendered fragment: no final newline, since a reader places it.
input_binding
The declaration of the flake input named input, in any of its forms — name = { … };, inputs.name.url = "…";, a compact or a quoted binding — as the text of its value.
nix_input_name
A flake input name for a package name: a Nix identifier, derived deterministically.
outputs_argument_present
Whether a flake’s outputs function head names input.
render
Render every token whose value is known, with a plain replace.
seed
One rendered seed file, its final newline kept.