Open nesadrian opened 2 weeks ago
It looks like this issue is more complex than what was first assumed. We should start by looking at init-order.js, order/index.js and layout.js in dagre to fix this issue. Use "yarn patch-package dagre" once the changes in the node module are done and the issue is resolved to apply the changes for each yarn install.
Remove comment in nodeValidityHelper.js once this is fixed
Even though the backend order seems to be correct, the frontend messes up the order of choice children. Probably related to the d3 hierarchy algorithm. I think this was fixed with the patch-package script, so start checking that first.