Replies: 2 comments
-
i think it's a litlle bit early
|
Beta Was this translation helpful? Give feedback.
-
No, I've tested it on most of my diagrams here and they come out better with dagre: https://github.com/HariSekhon/Diagrams-as-Code This also shouldn't be done before #410 and ample time and warnings across several versions for users to hardcode their layout engine within their d2 script files as per #1290. If anything, it perhaps should never be done because backwards compatibility is a bad user experience for anybody who has invested a lot of time in a technology. It'd be better to just make it a prominent setting recommendation in tutorials and docs and let users do it to avoid breaking existing things. I personally generate all my D2 diagrams via GitHub Actions CI/CD in that repo above and would be very unimpressed if one day they all got messed up by some change under the hood of d2. |
Beta Was this translation helpful? Give feedback.
-
Currently we use dagre, but with the recent improvements to ELK, I find myself choosing it more than dagre nowadays.
52 votes ·
Beta Was this translation helpful? Give feedback.
All reactions