-
Notifications
You must be signed in to change notification settings - Fork 607
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
Node/Edge ordering issue #189
Comments
Hey @alirussell its been 3 years :/ did you manage to resolve this? |
4 years, something new? |
something new? |
Disabling the optimal order heuristics fixes this. To do that, fork the repo and add a |
Any chance of getting it fixed? |
I have just solved this problem by a simple way via skipping the Post-conditions of ordering process. More specifically, I only add
"dagre": "0.8.5"
npm i -D patch-package
{
"script": {
"postinstall": "patch-package"
}
}
mkdir patches
touch patches/dagre+0.8.5.patch
|
dagre.layout(g, { disableOptimalOrderHeuristic: true }); |
This code works, thank you very much!👍 |
Im having an issue with keeping a consistent ordering of nodes/edges in my graph. The images below show how an extra node in the graph seems to completely change the ordering.
I am making sure that i use the same order for edges and nodes in each render, and I'm checking the init-order method and it seems to be ranking them in the correct order there, but somewhere it seems to be changing and i can't figure out why. i have checked out a few of the discussions about clustering and other order related issues, but can't see any solution.
I also didn't seem to get this with an older version, but i can't remember which version it was.
Any help would be much appreciated
The text was updated successfully, but these errors were encountered: