Doc system test

Post-template commands

How the commands that templates list are run in the target folder after files are written.

Meta block front matter of this doc
namespaces
  • durian.cloud/cyanprint/project-lifecycle
  • durian.cloud/cyanprint/authoring
type
algorithm
code
  • sulfone.iridium/cyanprint/src/command_executor.rs
  • sulfone.iridium/cyanprint/src/run.rs

Commands come from every template version in each current spec's tree, in run order. Interactive: one approval prompt, then each runs with sh -c in the target folder; on a failure the user picks go on or stop. Headless: all run without prompts, output goes to stderr, and any failure makes the command fail. They run after the state file is saved.

Where it lives

  • sulfone.iridium/cyanprint/src/command_executor.rs
  • sulfone.iridium/cyanprint/src/run.rs

Stub: summary only.