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

rank added as Config option for ER diagram #5738

Open
tah96 opened this issue Aug 22, 2024 · 0 comments
Open

rank added as Config option for ER diagram #5738

tah96 opened this issue Aug 22, 2024 · 0 comments
Labels
Status: Triage Needs to be verified, categorized, etc Type: Enhancement New feature or request

Comments

@tah96
Copy link

tah96 commented Aug 22, 2024

Proposal

I've seen in some diagrams (maybe historical) there was a config/directive that allowed "rank" to be passed which helped control the position of nodes/entities in a diagram.

Use case: When an ERD has 5+ entities connected to a single entity via relationships, this can be visually displeasing and get messy. To allow for "moving" of entities to certain levels, the "rank" here would help

Example


title: Order example

erDiagram
CUSTOMER ||--o{ ORDER : places
ORDER ||--|{ LINE-ITEM : contains
CUSTOMER }|..|{ MAILING-ADDRESS : uses
CUSTOMER }|..|{ SHIPPING-ADDRESS : uses
CUSTOMER }|..|{ PAYMENT-METHODS : uses
CUSTOMER }|..|{ USER-PROFILE : has

This will show 5 entities below CUSTOMER if dropped in the Live Editor. Would like to make it more true to a "Star" schema where Customer is at its own "level", Mailing-Address and Shipping Address are at its own level, Payment Methods and User-Profile at its own level

Screenshots

No response

@tah96 tah96 added Status: Triage Needs to be verified, categorized, etc Type: Enhancement New feature or request labels Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Triage Needs to be verified, categorized, etc Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant