Skip to main content

Module error

Module error 

Source
Expand description

Errors surfaced by the config crate.

See apimock_routing::error for the rationale on per-crate error types. ConfigError wraps RoutingError via #[from] so rule-set load failures flow through without the caller pattern-matching on origin.

§5.1.0 additions

  • WorkspaceError — surfaced by Workspace::load.
  • ApplyError — surfaced by Workspace::apply.
  • SaveError — surfaced by Workspace::save.

Each of the three “operation” errors wraps ConfigError via #[from] because the underlying cause of most workspace failures is a plain config load / write problem.

Enums§

ApplyError
Failure during Workspace::apply.
ConfigError
SaveError
Failure during Workspace::save.
WorkspaceError
Failure during Workspace::load. Currently a thin wrapper around ConfigError — kept as its own type so the Workspace API signals intent at the type level and has room to grow (e.g. “path is not a directory”, “no root config found”).

Type Aliases§

ConfigResult