Struct ScaffoldReport 

pub struct ScaffoldReport {
    pub root: PathBuf,
    pub files: Vec<PathBuf>,
    pub next_steps: Vec<String>,
    pub cargo_toml_registered: Option<bool>,
    pub registered: Option<bool>,
}

Report returned by both scaffolding functions: the paths written, so the binary can print them to the user.

Fields

root: PathBuf

Root directory the scaffold landed in (project dir, or plugins/<name>/).

files: Vec<PathBuf>

All files written, relative to root.

next_steps: Vec<String>

Post-scaffold instructions for the user. The binary prints these after the file list.

cargo_toml_registered: Option<bool>

Whether the project’s Cargo.toml was updated to include the new plugin as a path dependency. None means the operation wasn’t attempted (e.g. scaffold_project doesn’t auto-register). Some(true) = dep added, Some(false) = dep already present (idempotent — no duplicate written).

registered: Option<bool>

Whether the thing that was scaffolded is actually registered — the owner file (main.rs / the plugin’s lib.rs) now reaches it.

false when the tool could not edit the owner file and handed the user the lines instead. The caller MUST consult this before printing a success line: startcommand used to announce “Registered x on the App builder” purely because the user asked for --in root, whether or not it had managed to wire anything. The user read the success line, ran the command, and got unknown command — the CLI asserted a registration it knew it had not performed. None for scaffolders where registration isn’t a concept (startproject).

Trait Implementations

impl Clone for ScaffoldReport

fn clone(&self) -> ScaffoldReport

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ScaffoldReport

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.