Arrow of class diagram inheritance arrow missing

[lfuhr]

There are two options.

• Introduce another arrow like --i> , --[>, --o> or --|:>
• Change the black arrow --|> to be white

What do you think

[WolfgangFahl]

see #780

[WolfgangFahl]

see https://en.wikipedia.org/wiki/Class_diagram#/media/File:Uml_classes_en.svg

[fightinggg]

There are two options.

• Introduce another arrow like --i> , --[>, --o> or --|:>
• Change the black arrow --|> to be white

What do you think

I think so
Inheritance arraow should fill with white color

[wouterbeek]

+1 Mermaid deviates from most if not all other class diagram visualizations in this regard. It would be great if this could be fixed.

[mvf]

The arrow should be hollow (i.e. background color, which isn't necessarily white). For now, I'm using the following workaround in my config.json:

{
    "theme": "dark",
    "themeCSS": ".extension { fill: #1c1e1f !important; }"
}

Before:

After:

Unfortunately, one can't use transparent because then the arrows look like this:

It would be great if Realization and Association/Dependency arrows could be fixed too. The former have a dashed outline, and the latter have an unorthodox tented appearance instead of being just two solid lines.

[das-g]

The arrow should be hollow (i.e. background color, which isn't necessarily white).

Indeed. This is confirmed by https://www.uml-diagrams.org/generalization.html:

A generalization is shown as a line with a hollow triangle as an arrowhead between the symbols representing the involved classifiers. The arrowhead points to the symbol representing the general classifier. […]

[…]

… and by the UML 2.5 specification (PDF, section 9.2.4.2 "Other elements" on p. 100) …

A Generalization is shown as a line with a hollow triangle as an arrowhead between the symbols representing the
involved Classifiers. The arrowhead points to the symbol representing the general Classifier.

… with examples in section 9.2.5 on the following page:

[michalspano]

Any updates on this one? I like the tool a lot; it's just this inconsistency which makes it harder to use, regarding the solid triangle for inheritance.

[skogsbaer]

I would really appreciate an fix here. Mermaid is just plain wrong regarding generalization arrows.

[lfuhr]

I think we should make a point what solution developers should go for.

Give me a thumbs up here if you think
--|> should be changed to transparent.

[lfuhr]

Give me a thumbs up here if you think
it would be better to Introduce another arrow like --i> , --[>, --o> or --|:>

[lfuhr]

Give me a thumbs up here if you think
It is just fine as it is

[WolfgangFahl]

UML sets the standard so i think this could be a way to avoid further discussion:

[jgreywolf]

No reason to add a new arrow type at this point. Just to correct the arrow being used. I will look at this.