Layout is already copying the graph -- why not let it be immutable?

Just export each of the layout functions: buildLayoutGraph, runLayout, and updateInputGraph.

Also, you could just return the layoutGraph and let someone else merge it in if they want.

https://github.com/ciena-blueplanet/dagre/blob/master/src/layout.js#L416

• Why was this fork created?
• What problem was it solving?
• Why aren't these changes pushed into the upstream rather than in a fork?

In an upcoming project, I'll have need for directed-acyclic graph rendering and have had a few issues with cpettitt/dagre in the past. Seeing that it's now unmaintained, I started looking into this fork. I like the look of the work done so far. Are you aiming to be a general-use replacement for the original, open to public contributions?

Hi, thanks for taking care of dagre!

I am currently experimenting with clusters, clusterLabelPos:'top' and rankDir:'BT'. This leads to a layout where the nodes within a cluster are positioned over the cluster labels. Is there any chance to get them out of the way?

In dagrejs/dagre-d3#156 @cpettitt said:

"Looks good! It would be possible to get the edges to route around the cluster label by doing some of this in dagre - e.g. adding a dummy node to the cluster at the right rank with the size of the label."

Is it easy to add such dummy nodes?

Hi,

I installed your fork of dagre with npm install --ignore-scripts as written in the README.

But how do I build it? There is no dist folder.

Thx and best regards,

Josef

Will cytoscape-dagre work with this or would we need to fork out a ciena-cytoscape-dagre?

Waiting to hear back from the owner of https://github.com/cpettitt/dagre to see if we can take over the project and publish to npm. If not we will need to publish this under another name.

This will also mean updating any and all references (mainly in package.json).

We're built an organization around dagre and are resuming development. Would you be OK with us pulling some of your improvements back upstream, such as your work on lodash 4 support? Any interest in having a committer in the org for the upstream project?

This is more of a question- ^

I'm looking at this for reference but I can't understand why this is doing it differently
https://github.com/ciena-blueplanet/graphlib/blob/master/index.js

I'm trying to use this library with webpack, but it's not able to recognize the import keyword and it's exploding.