fix: Remove unsupported style separators from Mermaid subgraph declarations#974
Merged
fix: Remove unsupported style separators from Mermaid subgraph declarations#974
Conversation
…ations GitHub's Mermaid renderer doesn't support the `:::` style separator on subgraph declarations, causing parse errors. Removed `:::futureBlock` from ProcessMining subgraph and `:::safetyBlock` from SafetyGate subgraph. The individual nodes within these subgraphs still retain their styles (e.g., `:::future`), so visual styling is preserved where supported. Co-Authored-By: Claude Sonnet 4.5 <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.
Summary
:::futureBlockstyle separator from theProcessMiningsubgraph declaration:::safetyBlockstyle separator from theSafetyGatesubgraph declarationGitHub's Mermaid renderer doesn't support the
:::style separator on subgraph declarations, causing the following parse error:The individual nodes within these subgraphs still retain their
:::futureclass styles, so visual differentiation of future features is preserved.Test plan
🤖 Generated with Claude Code