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
I have searched the existing issues and this is a new bug.
Current Behavior
If you call $reset with a graph that has edges in the state, the @error event is emitted with an orphaned edge error for each removed edge.
Expected Behavior
$reset should reset the state without errors
Steps To Reproduce
Click reset in this sandbox and observe the console errors
Relevant log output
No response
Anything else?
This can be worked around by calling removeEdges(unref(getEdges)) before $reset (as long as all edges are deletable or made deletable beforehand). It seems like maybe the code internally just processes nodes before edges?
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
If you call
$reset
with a graph that has edges in the state, the@error
event is emitted with an orphaned edge error for each removed edge.Expected Behavior
$reset should reset the state without errors
Steps To Reproduce
Click reset in this sandbox and observe the console errors
Relevant log output
No response
Anything else?
This can be worked around by calling
removeEdges(unref(getEdges))
before$reset
(as long as all edges are deletable or made deletable beforehand). It seems like maybe the code internally just processes nodes before edges?The text was updated successfully, but these errors were encountered: