Currently, we use the neat gross hack of using "*" edges as drop-zones for ad-hoc wires. This works as long as we don't need the wires to connect two ports with different names. I ran into this being a problem when re-building the Tour Guide Writer in the visual editor: the inputs to the runJavascript node where the guides and the locations are being assembled conflict, since both guides and locations are now named list. I had to resort to using a jsonata node simply to rename the port name:
Ideally, I would have been able to name and rename the ad-hoc ports as I was adding them to the runJavascript node.
dglazkov
commented
4 months ago
Currently, we use the
neatgross hack of using "*" edges as drop-zones for ad-hoc wires. This works as long as we don't need the wires to connect two ports with different names. I ran into this being a problem when re-building the Tour Guide Writer in the visual editor: the inputs to therunJavascriptnode where the guides and the locations are being assembled conflict, since bothguidesandlocationsare now namedlist. I had to resort to using ajsonatanode simply to rename the port name:Ideally, I would have been able to name and rename the ad-hoc ports as I was adding them to the
runJavascriptnode.