pub struct BpmnMappingBlocker {Show 24 fields
pub rule: Rule,
pub rule_number: i32,
pub message: String,
pub element_id: Option<String>,
pub flow_id: Option<String>,
pub message_name: Option<String>,
pub kind: Option<String>,
pub from: Option<String>,
pub to: Option<String>,
pub target: Option<String>,
pub target_flow: Option<String>,
pub from_kind: Option<String>,
pub to_kind: Option<String>,
pub from_message: Option<String>,
pub to_message: Option<String>,
pub expected_scope: Option<String>,
pub actual_scope: Option<String>,
pub mapped_source: Option<String>,
pub mapped_target: Option<String>,
pub sources: Option<Vec<String>>,
pub targets: Option<Vec<String>>,
pub candidates: Option<Vec<String>>,
pub missing: Option<Vec<String>>,
pub unexpected: Option<Vec<String>>,
}Expand description
BpmnMappingBlocker : One reason a mapping document does not hold for a version pair (#925). rule is the discriminant; rule_number groups it (1 document well-formedness; 2 no silent drop – an unmapped, deleted element would drop a token; 3 stable meaning – kind, message binding and correlation names; 4 injectivity – no N:1 merge, because a join’s arrived is a set and would absorb the duplicate; 5 scope coherence; 6 edge images – each source flow needs a unique counterpart between its mapped endpoints; 7 join coherence – the only silent failure, since JoinState.expected is derived once and never refreshed; 8 boundary coherence – the interruption surface of a running activity must not change under it). The remaining properties are the rule’s own, and which are present depends on rule.
Fields§
§rule: Rule§rule_number: i32§message: Stringthe rendered sentence, safe to show an operator as-is
element_id: Option<String>§flow_id: Option<String>§message_name: Option<String>§kind: Option<String>§from: Option<String>§to: Option<String>§target: Option<String>§target_flow: Option<String>§from_kind: Option<String>§to_kind: Option<String>§from_message: Option<String>§to_message: Option<String>§expected_scope: Option<String>§actual_scope: Option<String>§mapped_source: Option<String>§mapped_target: Option<String>§sources: Option<Vec<String>>§targets: Option<Vec<String>>§candidates: Option<Vec<String>>§missing: Option<Vec<String>>§unexpected: Option<Vec<String>>Implementations§
Source§impl BpmnMappingBlocker
impl BpmnMappingBlocker
Sourcepub fn new(rule: Rule, rule_number: i32, message: String) -> BpmnMappingBlocker
pub fn new(rule: Rule, rule_number: i32, message: String) -> BpmnMappingBlocker
One reason a mapping document does not hold for a version pair (#925). rule is the discriminant; rule_number groups it (1 document well-formedness; 2 no silent drop – an unmapped, deleted element would drop a token; 3 stable meaning – kind, message binding and correlation names; 4 injectivity – no N:1 merge, because a join’s arrived is a set and would absorb the duplicate; 5 scope coherence; 6 edge images – each source flow needs a unique counterpart between its mapped endpoints; 7 join coherence – the only silent failure, since JoinState.expected is derived once and never refreshed; 8 boundary coherence – the interruption surface of a running activity must not change under it). The remaining properties are the rule’s own, and which are present depends on rule.
Trait Implementations§
Source§impl Clone for BpmnMappingBlocker
impl Clone for BpmnMappingBlocker
Source§fn clone(&self) -> BpmnMappingBlocker
fn clone(&self) -> BpmnMappingBlocker
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more