Details
-
Sub-task
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
Description
Currently the definitions of the state transitions are scatter between multiple state contexts. We want to:
- Getting rid of duplicate definitions
- Attempt to make the state transitions less confusing for the "code reader"
This will allow "code reader" to use a type hierarchy for understanding which transitions are allowed from which state. (see the attached screenshot)
Attachments
Attachments
Issue Links
- links to