errors#

The failure types. Every fallible call in the crate returns Result<_, Error>, and Error wraps one of two causes. InputError means the data or options you passed are invalid, with its kind in InputErrorKind. ProjectError means the call doesn't fit the project's current state. Conflicts, cycles and rejected apply operations aren't errors: they come back as data inside Ok. All four types are re-exported at the crate root, so you import plen_core::Error, not an internal module path.

For recovery patterns, see Error handling.

• ErrorThe error type of every fallible call in plen-core
• InputErrorInvalid data or options passed to a call, with the field path that failed
• InputErrorKindWhether invalid input failed to decode or failed semantic validation
• ProjectErrorA call that doesn't fit the project's current state, such as a missing or stale baseline