Skip to content

fix(session-ui): render sequence labels with semicolons - #46990

Closed
Hona wants to merge 1 commit into
anomalyco:v2from
Hona:mermaid-labels
Closed

Hona wants to merge 1 commit into
anomalyco:v2from
Hona:mermaid-labels

Conversation

@Hona

@Hona Hona commented Sep 3, 2026

Copy link
Copy Markdown
Member
  • The reported sequence diagram fell back to code because Mermaid treats ; in Check permissions; create pending request as a statement separator.
  • Retry rejected sequence diagrams with message-label semicolons escaped as #59;. Keep valid diagrams, existing entity escapes, the original Markdown, and unrecoverable-input fallback unchanged.
  • Use the reported request/reply diagram in the production timeline story.
Before After
Sequence diagram falls back to source code The same sequence diagram renders all ten messages

Copilot AI lite review requested due to automatic review settings September 3, 2026 06:21

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@github-actions

github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants