You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To achieve parsing of DOT files, there is some preparation work to be done:
Implement the comments (//, /* */ and #)
Introduce a new Document object, as the comments and spaces can be before or after the graph object.
Given that this doable work is done, a parser would still have some limitations:
The graph would be re-formatted (custom spacing lost)
New instructions would be added at the end of the graphs
I don't know what you require exactly for your specific case, but if that's OK for you with those limitations I can maybe work on that in the coming weeks.
To achieve parsing of DOT files, there is some preparation work to be done:
Implement the comments (//, /* */ and #)
Introduce a new Document object, as the comments and spaces can be before or after the graph object.
Given that this doable work is done, a parser would still have some limitations:
The graph would be re-formatted (custom spacing lost)
New instructions would be added at the end of the graphs
I don't know what you require exactly for your specific case, but if that's OK for you with those limitations I can maybe work on that in the coming weeks.
These restrictions do not affect my needs, thanks for your work!🥰
Nice work!
But I have a requirement to read the generated .dot, modify the nodes/edges of the .dot file, and then generate a new .dot
It seems like a new parsing function needs to be added.
Looking forward to your reply.
Best wishes,
Porlockzzz
The text was updated successfully, but these errors were encountered: