Snake like chart of architecture-beta in flowchart

[mayankdmishra]

I get snake like flow in architecture-beta with a:R --> L:b logic
`architecture-beta
group api(cloud)[API]

service db(database)[Database] in api
service d1(disk)[Storage] in api
service d2(disk)[Storage] in api
service sr(server)[Server] in api

sr:R --> L:db
db:B --> T:d1
d1:L --> R:d2`

Why this logic is not available in flowchart? If possible how can i get the snake flow in flowchart?
`flowchart
lt1["left"]
rt["Right"]
dn["Down"]
lt2["left2"]

lt1:L --> R:rt
rt:B --> T:dn
dn:R --> L:lt2`

This logic doesn't work in flowchart.

[farfromexact]

architecture-beta and flowchart are different syntaxes and layout engines. Endpoint annotations such as 'sr:R -- > L:db' are understood by the architecture-beta grammar, but ordinary flowchart does not interpret them as port constraints. That is why the same text does not produce the same routing.

For a normal flowchart, choose the overall direction with flowchart LR or flowchart TD and use intermediate nodes or subgraphs if you need a snake-like visual. The exact edge routing is still layout-engine dependent. If port-level connections are essential, architecture-beta or another diagram engine with explicit ports is the better fit.

Adding endpoint syntax to flowchart would be a feature request rather than a syntax correction. A minimal example showing the desired layout and whether the direction must be deterministic would help maintainers judge whether a new layout option is feasible.

[mayankdmishra]

Thanks @farfromexact for ur reply and clearing that flowcharts doesn't use the same logic as architecture-beta at the endpoint level.
Yes I wll put a feature request. Also if you can tell me how can i contribute for this feature?