Fix mermaid rendering in repo transforms #115
Merged
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.
Root cause was in
remote-content/remote-sources/repo-transforms.js: the HTML comment cleanup blindly replaced every -->, so Mermaid arrows like A-->B turned into */} during the remote-content sync.The reason we have that transform in the first place raw
<!-- ... -->comments are valid in Markdown but not in MDX. When Docusaurus runs MDX, those comments are treated as JSX and cause build-time syntax errors.Updated the transform to rewrite only actual HTML comments, leaving Mermaid syntax intact. This prevents the bad replacement and keeps diagrams renderable.