onEdgeUpdate crashes when using CustomEdge and loose connectionMode
See original GitHub issueSo I am not sure if it is an issue with my setup but if I set the connectionMode to loose and try to drag the edge from one node to another I get the following issue:

It is occurring because the connectionHandleType for target is a null array. I think it should be an empty array instead.

Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
onEdgeUpdate crashes when using CustomEdge and loose ...
onEdgeUpdate crashes when using CustomEdge and loose connectionMode - TypeScript react-flow. So I am not sure if it is an issue with my...
Read more >Fix Illustrator crash issues
Unable to open Illustrator? Illustrator crashing or freezing? We're here to help!
Read more >Outlook crashes or stops responding when used with Office ...
This article describes how to troubleshoot Microsoft Outlook when it's used together with Microsoft 365 and: Outlook stops responding (hangs).
Read more >Random crashes while launching or working in Fusion 360
The program closes unexpectedly with no error report. The recovery files are almost never available. Fusion 360 suddenly crashes the ...
Read more >Crashes and issues
Data about your current browsing session including open tabs, location on the page, form data, etc. Extension Cookies, Cookies associated with your installed ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I should have read the title of this issue more carefully 😉 It’s about the
onEdgeUpdate… I will check that. It seems like a bug.Yes, and I found the issue is fixed by using
useUpdateNodeInternals… so going to close this one 😃