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
When a graph is used as a subgraph through components/Graph.coffee the defaults are always sent regardless of whether the parent graph has an attached socket. This may require checking socket count in the Network.sendDefaults method on the socket.to property.
Something like:
for socket in@defaultscontinueunlesssocket.to.sockets.lengthis1socket.connect()
socket.send()
socket.disconnect()
Or maybe a more specific socket check:
for socket in@defaultscontinueunlesssocket.to.sockets.lengthis1anddeepEquals(socket, socket.to.sockets[0])
socket.connect()
socket.send()
socket.disconnect()
This may not be the optimal way to handle it. Other options would be to investigate whether defaults should be removed as a socket is attached to a subgraph or refreshing a network's defaults from the parent.
** The coffee syntax might not be correct, just throwing the ideas out here for now.
The text was updated successfully, but these errors were encountered:
When a graph is used as a subgraph through
components/Graph.coffee
the defaults are always sent regardless of whether the parent graph has an attached socket. This may require checking socket count in theNetwork.sendDefaults
method on thesocket.to
property.Something like:
Or maybe a more specific socket check:
This may not be the optimal way to handle it. Other options would be to investigate whether defaults should be removed as a socket is attached to a subgraph or refreshing a network's defaults from the parent.
** The coffee syntax might not be correct, just throwing the ideas out here for now.
The text was updated successfully, but these errors were encountered: