Expand description
Configuration trait and validation types for mcpr modules.
Each mcpr module (store, cloud, tunnel, logging, etc.) implements ModuleConfig
on its TOML config section struct. This lets every module own its own defaults,
validation logic, and documentation — while the CLI orchestrates validation by
iterating over all registered modules.
§Design rationale
Without this trait, all config validation lives in one monolithic function in
mcpr-cli/src/config.rs, and every new module must touch that file. With it,
each crate validates itself — the CLI just loops over &[&dyn ModuleConfig].
Structs§
- Config
Issue - A single validation issue found in a module’s configuration.
Enums§
- Severity
- How serious a configuration issue is.
Traits§
- Module
Config - Trait for module-owned configuration sections.