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
idea: since there will undoubtedly be graphviz properties that aren't first-class properties in Kite, we could hold these extraneous properties in a Dict String String. that way, we should be able to import a .dot file and then export an equivalent .dot, without losing those properties.
i haven't looked at how feasible this is at an implementation level. maybe it complicates things more than it's worth.
The text was updated successfully, but these errors were encountered:
erkal
changed the title
idea: since there will undoubtedly be graphviz properties that aren't first-class properties in Kite, we could hold these extraneous properties in a Dict String String. that way, we should be able to import a .dot file and then export an equivalent .dot, without losing those properties.
prevent losing the properties in a dot file that is not generated by Kite
Apr 19, 2019
idea: since there will undoubtedly be graphviz properties that aren't first-class properties in Kite, we could hold these extraneous properties in a
Dict String String
. that way, we should be able to import a.dot
file and then export an equivalent.dot
, without losing those properties.i haven't looked at how feasible this is at an implementation level. maybe it complicates things more than it's worth.
Originally posted by @brandly in #4 (comment)
The text was updated successfully, but these errors were encountered: