Skip to content
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

classDiagram - New version fails in some relationships #109

Open
gcosta87 opened this issue Nov 15, 2024 · 0 comments
Open

classDiagram - New version fails in some relationships #109

gcosta87 opened this issue Nov 15, 2024 · 0 comments

Comments

@gcosta87
Copy link

gcosta87 commented Nov 15, 2024

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

classDiagram
   class MyClass {
    value: String
   }

   MyClass o--> "0..N" MyClass: blocks
   MyClass o--> "0..N" MyClass: require

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
imagen
imagen

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant