-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix/5741 unique marker ids #5756
base: develop
Are you sure you want to change the base?
Conversation
|
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
I don't know why Lint fails here on GitHub (the “Some checks were not successful”). It works fine on my machine. Of note too: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove this file from the PR?
commit: |
📑 Summary
Ensures unique IDs for the markers. This extends merge #4825, to cover C4 context diagrams, Entity Relationship diagrams, Requirement diagram, Sequence diagrams, Timelines, and User Journeys.
Resolves #5741, #1318 and #3267 (that were closed while only partially resolved), mjbvz/vscode-markdown-mermaid/#270.
Also, adds classes to the markers for future and/or custom styling purposes.
📏 Design Decisions
Markers IDs are replaced by
<svg_id>-<marker_id>
, where:<svg_id>
is the ID of the SVG element (the Mermaid diagram)<marker_id>
is the previously used id.The added classes use the format:
mermaid-marker-<diagram_type>-<marker_id>
(e.g.,mermaid-marker-er-ONLY_ONE_END
), where<diagram_type>
is a shorthand for the diagram type:C4Context
) →c4
erDiagram
) →er
journey
) →journey
requirementDiagram
) →req
sequenceDiagram
) →seq
timeline
) →tl
Those changes have also been implemented for seemingly unused markers found in the code.
📋 Tasks
Make sure you
MERMAID_RELEASE_VERSION
is used for all new features.pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.