Repository navigation
Fork: multi-target transitions fail the reachability check and are not documented as UML fork #705
Description
Why
a.to([P.r1.x2, P.r2.y2]) is how a UML fork is written here, but statemachine/graph.py follows only the first target, so a class whose y2 has no other incoming transition raises "unreachable states ['y2']". IO-loaded documents skip that validator, which is why SCXML and PSSM cases never hit it.
Scope
- The reachability walk follows every target of a transition.
- Document multi-target transitions as the UML fork.
Acceptance
A regression test on a Python class fails before and passes after; the fork PSSM case keeps passing.
Refs #692
Activity