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
Right now, RelationshipView contains the Relationship which is a PropertyHolder, but the RelastionshipView (although it has its own name and description) does not provide properties.
Still, that could be helpful especially in SequenceDiagrams where multiple dependencies between two components could be shown in parallel and different properties could be printed on the diagram on each connector, but right now we can only use alsways the same getProperties() from the underlying Relationship
Letting RelationshipView be a PropertyHolder would be a quite straight-forward; what we would need to come up with is a strategy how (and if) to delegate to the relationship.getProperties() when printing diagrams.
Priority
I'm willing to add this feature myself and raise a PR (please confirm approach first)
More information
No response
The text was updated successfully, but these errors were encountered:
Description
Right now,
RelationshipView
contains theRelationship
which is aPropertyHolder
, but theRelastionshipView
(although it has its ownname
anddescription
) does not provide properties.Still, that could be helpful especially in SequenceDiagrams where multiple dependencies between two components could be shown in parallel and different properties could be printed on the diagram on each connector, but right now we can only use alsways the same
getProperties()
from the underlyingRelationship
Letting
RelationshipView
be aPropertyHolder
would be a quite straight-forward; what we would need to come up with is a strategy how (and if) to delegate to therelationship.getProperties()
when printing diagrams.Priority
I'm willing to add this feature myself and raise a PR (please confirm approach first)
More information
No response
The text was updated successfully, but these errors were encountered: