visualiser: Create custom branching name to avoid collision #40
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.
Currently for any branching that takes place the branching name in the
md
file isif_state
which means that if there is more than one branching in the workflow the visualiser will incorrectly connect the branching due to referencingif_state
. Instead using thefrom
value and adding a suffix of_branching
allows the output to be1_branching
which indicates from node1
branching to node2
and is represented like such: