M Xu
M Xu
ok - seems like the spec is out of date. makes it hard to generate a client using the out of date spec.
is this something involving webpack? also seeing this error on every load, but i think its unrelated - 
anyone? initial mounting seems to take up a lottt of time.
how does this address #201? im looking for that functionality but dont see how this maps to the ability to incrementally layout a new node to a graph.
im having this issue as well  the line at the bottom left doesnt make much sense. would building a recreateable test case help? im happy to do whatever it...
@graymur if you replace those lines then is the idea that you can call layout(), then addNode(), then layout() on the same dagre graph and get some level of stability...
yeah - what is a 'control point..?'
was able to make a small fix in react-dnd https://github.com/react-dnd/react-dnd/issues/1368
i was able to get the correct behavior for refreshing row height while dragging on my own local fork of react-sortable-tree. the changes probably are not usable by anyone else,...