pub struct WorkflowIssue {
pub code: IssueCode,
pub message: String,
pub path: Option<String>,
pub task_id: Option<String>,
}Expand description
One problem with a workflow definition.
Shared by Workflow::validate_authored and, from the registry side,
EngineBuilder::check_workflow. Both fill what they genuinely know: a
definition check always has an authored coordinate and knows the step id
when the problem concerns a step; a registry check always has a task id and
reports a path relative to that task.
Fields§
§code: IssueCodeStable machine-readable classification.
message: StringHuman-readable explanation. Not stable — branch on Self::code.
path: Option<String>Where the problem is. From Workflow::validate_authored this is the
coordinate the author typed, rooted at the workflow document:
tasks[1].tasks[0].id.
task_id: Option<String>The step this concerns, when it concerns one. Step ids are unique across tasks and groups, so this identifies a step on its own.
Implementations§
Source§impl WorkflowIssue
impl WorkflowIssue
Sourcepub fn severity(&self) -> Severity
pub fn severity(&self) -> Severity
When this issue bites — IssueCode::severity of Self::code.
Screening before a build is the point: everything but
Severity::Advisory means the workflow will not do what it says.
Trait Implementations§
Source§impl Clone for WorkflowIssue
impl Clone for WorkflowIssue
Source§fn clone(&self) -> WorkflowIssue
fn clone(&self) -> WorkflowIssue
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more