Enhance *State/Mode classes with incoming and outgoing StateTransition accessors #455
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello py-capellambse team, and thank you very much for this great project and especially for the amazing contributor experience!
I'm interested in working with
StateMachine
s and the relations within and around them, so I noticed #426 which I'll now stop spamming with mentions. To start from the relatedStateTransition
s, this PR adds:incoming_transitions
outgoing_transitions
Please check the commits for the detailed lists of classes impacted, which can also be rolled back to just
State
.The PR also adds test cases for both of these new accessors on
State
, and forInitialPseudoState.outgoing_transitions
; I couldn't find aStateMachine
with aFinalState
to write the test case forFinalState.incoming_transitions
but it should be easy to add with the right UUIDs.Thanks in advance!