-
Notifications
You must be signed in to change notification settings - Fork 86
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
Is there a lang spec documenting how model files in elk and json are to be defined ? #1064
Comments
BTW this is a snipet of the json that generated from the engine now with the above model {
"id": "mur_2491043083",
"sources": [
"mur_809189348"
],
"targets": [
"mur_1572453709"
]
},
all sections and points are missing. I was hoping that the engine would fail if something is semantically wrong in the graph. so it is succesful but it is not returning useful data here is the plain java code i am using to convert the elk file to json. Please let me know if the way i am doing is wrong by any chance |
this think is correctly generated in that the ui does not complain about it but i am still getting no sections for the
|
Here is a small example for edges and were they should be in the graph hierarchy. Does this answer your question? |
thank you for that quick response
|
|
Great explanation i am mostly getting there
just to be clear i assume a0->a1->a2->a3 (-> here means left hand side is parent of righ hand side ) |
An edge from a1 to b2 is not directly possible. You would need an edge from a1 to a0 in a0, a0 to b0 at top level, b0 to b1 in b0, and b1 to b2 in b1 with ports inbetween. |
Thank you for that explanation i am starting to understand now ! |
Ask your questions
i have this large model ( i could not get a link from the web model )
I am trying to understand how to specify edges between nodes in my graph. unfortunately i cant grasp the logic of what is allowed and what is not allowed when specifying edges. specifying nodes was super simple to understand (from my untrained eyes). edges .. not so much :-)
to give context. my graph is autogenerated so from that angle i was hoping i could generate all edges at the end ( like the graph i have linked above) but it looks like that is not allowed.
I also tried putting the edges in the parent of the node being the source but also that failed. for example if the target node is on the top of the graph the sugestion from the editor was to put it on the top.
another question is: are the rules the same for elk files and json ? if its easier for me to generate the json maybe i will switch to using json instead.
(Optional) Expected behavior
a simple way to defined edges between nodes when the graph is hierarchical and multiple nested levels
(Optional) ELK Version
snapshot
The text was updated successfully, but these errors were encountered: