You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The new version of Mermaid changed the way some relationships are rendered in classDiagram. Especially the relationships of a class to itself.
On the other hand, and being less critical, in large diagrams with namespaces, those classes that have several relationships with others, tend to overlap more frequently.
To reproduce the other (less severe) bug requires a large diagram (30 classes and some namespaces)
Expected behavior
The MyClass class has two clear relationships with itself: blocks and requires.
Screenshots
Desktop (please complete the following information):
OS: Linux
Browser: Firefox
Version: 132
Additional context
I notice this change when I have an active class design project, and I usually compare it with the VSCode rendering (which uses an older version of the mermaid engine)
The text was updated successfully, but these errors were encountered:
Describe the bug
The new version of Mermaid changed the way some relationships are rendered in classDiagram. Especially the relationships of a class to itself.
On the other hand, and being less critical, in large diagrams with namespaces, those classes that have several relationships with others, tend to overlap more frequently.
To Reproduce
Just render this example diagram
To reproduce the other (less severe) bug requires a large diagram (30 classes and some namespaces)
Expected behavior
The MyClass class has two clear relationships with itself: blocks and requires.
Screenshots
Desktop (please complete the following information):
Additional context
I notice this change when I have an active class design project, and I usually compare it with the VSCode rendering (which uses an older version of the mermaid engine)
The text was updated successfully, but these errors were encountered: