-
Notifications
You must be signed in to change notification settings - Fork 2
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
Coaleace associations into single arrow #9
Comments
This should be doable, and it should be up to the 'writer' to decide how to represent these relationships. Mermaid can only do single-headed arrows. PlantUML can do no-headed lines. But a writer can assess if there are relationships in both directions and choose to represent them accordingly. Certainly the PlantUML writer should be able to assess if there are associations in both directions between two nodes, and consolodate them into a single no-headed arrow. Furthermore, in future, where associations are tagged, PlantUML could identify if more than one association connects in a single direction and consolidate into a single, one-directional arrow without a tag |
A model now already combine multiple connections with a '...' label (although this is argubly the writer's responsibility). |
7f13ad2 moved the '...' logic to the view, where it probably belongs |
A system, at the zoomed out, top-level view, may have associations between items that represent multiple connections at a low-level view.
For example a user may interact with a hi-fi system in multiple ways: drive volume control, drive input select, receive sound, receive status indicators.
The question is how to represent the implicit relationships. Should the two be connected with a single, no-arrow-headed line? Or two arrows in each direction?
The text was updated successfully, but these errors were encountered: