Struct InitService 

pub struct InitService;

Implementations

impl InitService

pub fn new() -> InitService

Create a new InitService

pub async fn create_project_directories(&self, path: &Path) -> Result<(), Error>

Create all the necessary directories for a new Mecha10 project.

pub async fn add_example_node( &self, project_root: &Path, component_name: &str, ) -> Result<(), Error>

Add an example node from the catalog to the project, updating Cargo.toml and mecha10.json as needed.

Per-node capabilities no longer exist - the caller (handlers/init.rs) is responsible for recomputing ProjectConfig::capabilities (the flattened top-level field) once, after its whole node-add loop finishes, via mecha10_cli_core::types::project::recompute_capabilities.

pub async fn sync_node_capabilities( &self, project_root: &Path, component_name: &str, is_monorepo_node: bool, ) -> Result<(), Error>

Ensure a node that’s already fully scaffolded on disk (component files already written, Cargo.toml/workspace member already present) also has a nodes map entry in mecha10.json, without re-running any of Self::add_example_node’s file-writing steps.

mecha10 init --update needs this: re-running the full add_example_node scaffold for a node that already has a local config.json would needlessly rewrite its component files (clobbering anything the project author customized) just to ensure one entry in mecha10.json. This only touches the nodes map entry, via Self::add_node_to_config’s upsert rules.

Trait Implementations

impl Default for InitService

fn default() -> InitService

Returns the “default value” for a type.