Enum ConfigError 

#[non_exhaustive]
pub enum ConfigError {
    ConfigRead {
        path: PathBuf,
        source: Error,
    },
    ConfigParse {
        path: PathBuf,
        canonical: Option<PathBuf>,
        source: Box<Error>,
    },
    PathResolve {
        path: PathBuf,
        source: Error,
    },
    Validation {
        reason: String,
    },
    RuleSet(RoutingError),
}

#[non_exhaustive] (RFC 041)

An enum’s own fields stay constructible across the crate boundary — #[non_exhaustive] on an enum restricts matching, not building its existing variants. What it forbids is an exhaustive match with no wildcard arm, since a future variant would otherwise make this a silent non-breaking-looking compile error downstream:

use apimock_config::ConfigError;

fn describe(e: &ConfigError) -> &'static str {
    match e {
        ConfigError::ConfigRead { .. } => "read",
        ConfigError::ConfigParse { .. } => "parse",
        ConfigError::PathResolve { .. } => "path",
        ConfigError::Validation { .. } => "validation",
        ConfigError::RuleSet(_) => "rule_set",
        // no `_` arm — exhaustive matches outside the crate must
        // carry one once the enum is `#[non_exhaustive]`.
    }
}

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

ConfigRead

The config TOML file could not be read from disk.

Fields

path: PathBuf

source: Error

ConfigParse

The config TOML file was read, but could not be parsed.

Fields

path: PathBuf

canonical: Option<PathBuf>

source: Box<Error>

PathResolve

A path on disk could not be resolved.

Fields

path: PathBuf

source: Error

Validation

Startup-time validation failed. reason is the first failure encountered (RFC 065) — previously a bare unit variant whose only detail lived in a log::error! call at the failing validator’s own site, which never reached a caller with no logger installed (apimock validate/get/set/match-test, none of which do).

Fields

reason: String

RuleSet(RoutingError)

A rule-set file failed to load or parse. Wraps the routing crate’s error type.

Implementations

impl ConfigError

pub fn kind(&self) -> ConfigErrorKind

Trait Implementations

impl Debug for ConfigError

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

Formats the value using the given formatter.

impl Display for ConfigError

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

Formats the value using the given formatter.

impl Error for ConfigError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl From<ConfigError> for WorkspaceError

fn from(source: ConfigError) -> Self

Converts to this type from the input type.

impl From<RoutingError> for ConfigError

fn from(source: RoutingError) -> Self

Converts to this type from the input type.