Repository navigation
diagram: replace ; in sequenceDiagram message and note text - #64
Merged
Merged
Conversation
A semicolon separates statements in Mermaid, and sequence message text is unquoted — so `A->>B: one thing; another` parses as two statements and the block fails to render, with the second half's first word read as an actor. Scoped to sequence blocks. A flowchart label is quoted, so a `;` there is safe; rewriting it would change prose to fix a problem that grammar does not have. An em dash rather than `;`: the entity does make the block parse, but it renders literally as `&;`, which is readable-but-wrong and worse than a clear substitution. A semicolon in this prose always joins two clauses. 7 tests, including that a clean block is returned byte-identical, that a colon inside the text is not treated as the boundary, and that a participant declaration is not mistaken for a message. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A semicolon separates statements in Mermaid, and sequence message text is unquoted — so
A->>B: one thing; anotherparses as two statements and the whole block fails to render, with thesecond half's first word read as an actor.
Follows #63. Same underlying class — generated prose landing in a position where Mermaid has a
metacharacter — in a different grammar.
Scope. Sequence blocks only. A flowchart label is quoted, so a
;there is safe; rewriting itwould change prose to fix a problem that grammar does not have. Verified both ways.
An em dash, not
;. The entity does make the block parse, but it renders literally as&;— readable-but-wrong, which is worse than a clear substitution. A semicolon in this prose always
joins two clauses.
7 tests, including that a clean block comes back byte-identical, that a colon inside the message
text is not treated as the boundary (file:line citations are common there), and that a
participantdeclaration is not mistaken for a message. 361 passing.
🤖 Generated with Claude Code