bugfix(mermaid): circumvents mermaid edge naming ambiguities #709
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.
Description
Motivation and Context
There's some interesting edge cases in the mermaid flowchart language. These two seemingly equal flowcharts render differently. Reason is that
o-->
is an arrow shape. Two ways to fix ito --> a
) -> this would make the generated .mmd larger, so we'll bump into mermaid's maximum input limit fastero
andx
). Easiest way to accomplish that is to uppercase the 'minified' node names.How Has This Been Tested?
Types of changes
Checklist
馃摉
鈿栵笍