-
Notifications
You must be signed in to change notification settings - Fork 87
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
no exported class LayoutDagRoot, LayoutDagNode, LayoutChildLink #57
Comments
This was by design. Dags are supposed to be created with any of the creation functions ( Is there a reason why you need to create nodes manually? I'm not overly opposed to exporting them, but I would want to see a compelling argument to. Part of the benefit of "controlling" dag creation is to prevent someone creating a cycle or something else which would break expected invariants around dags. you also point to the fact that: |
can you provide detailed typescript example/doc/urls of using connect(), hierarchy(), stratify() ? |
by the way... this link was broken https://erikbrinkman.github.io/d3-dag/ |
Thanks for pointing that out. I just fixed the documentation which should be up now and should answer your questions. There was an update to typedoc, so unfortunately some of the links in the documentation are going to be broken until I fix it, but it should be pretty easy to figure out where they were pointing. If you already have typescript objects that look like a dag, then you can use
then you could create a dag with:
|
ok, looks good this also raises another question: |
Look at the documentation (which unfortunately seems to do a poor job with the typescript annotations, the source is probably a better place to turn). Instead of children you can use |
As of version 0.7 (which has some breaking changes), the full build should be pushed, so importing from |
A new version 0.8 which is effectively 1.0-rc is out. The documentation should be up to date and mostly working, although there are probably a few missing things here and there. Everything is updated, although I did remove the ability to create your own nodes automatically. Let me know if you're still unable to do what you want. Otherwise I'm going to close this in a week or so. |
Hello,
the following classes are not exported: LayoutDagRoot, LayoutDagNode, LayoutChildLink.
I tryed to import theses classe, and use them directly to build with custom code the DAG graph.
Maybe I could use directly some other graph builder operator?
I did not understand the doc, and what is effectively exported/private from the doc
Thanks for your answer, or fix
The text was updated successfully, but these errors were encountered: