-
Notifications
You must be signed in to change notification settings - Fork 22
Open
Description
As far as I can tell, this doesn't support records? Is that correct?
I could only manage half a workaround; by using a custom "record" shape, and a manually encoded node label (e.g., <f0> a|<f1> b|<f2> c)) I could handle the nodes, but I can't figure out any way to get it to write edges as "node":f0 -> "node":f1 or node:f0 -> node:f1.
As far as the api goes, edge .From and .To just need to accept optional ports, and nodes need to accept a list of port names and labels (that can be nested in complicated ways, to be fair; they can be grouped in order to switch between horizontal fields and vertical fields).
rvinowise
Metadata
Metadata
Assignees
Labels
No labels