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
However, this workaround is ambiguous as you need to define which part belongs to which class. This makes reading the cardinalities in a fast way impossible.
Given the fact that it's possible to use aggregations and compositions arrows there should be support to define the cardinalities. The syntax for this could look like this, where the seperator is another colon
Class01 *-- AveryLongClass : 1 : 1..n
Loading
or with any other seperator char, like a pipe
Class01 *-- AveryLongClass : 1 | 1..n
Loading
If there is no seperator char it should be placed as an ordinary label.
The text was updated successfully, but these errors were encountered:
In UML diagrams the cardinalities are written next to the class they belong to.
This is not possible in mermaid currently. A workaround for this would be to write the cardinalities in the label of arrow.
However, this workaround is ambiguous as you need to define which part belongs to which class. This makes reading the cardinalities in a fast way impossible.
Given the fact that it's possible to use aggregations and compositions arrows there should be support to define the cardinalities. The syntax for this could look like this, where the seperator is another colon
or with any other seperator char, like a pipe
If there is no seperator char it should be placed as an ordinary label.
The text was updated successfully, but these errors were encountered: