Project broken since 6.0.0
See original GitHub issueHey,
Since update 6.0.0 my custom drag functionality is not working anymore. I can’t grab a node on the canvas anymore and my transitions/animations inside my custom edges for dropzones are not working anymore as well. For the custom drag, I used react-dnd. Do you have any idea what could have caused this?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Context with store has been broken since 6.0.0 #1645 - GitHub
I have received new outdated react project that suffers from abandoned and outdated packages. One of the main reason of its sufferings is...
Read more >Projects do not load in Visual Studio 2022 if .NET SDK 6.0.100 ...
After spending a lot of time, I have found the issue. It is .NET SDK 6.0.100-preview.5 the culprit.. If install .NET SDK 6.0.100-preview....
Read more >python project error: flake8-broken-line 0.6.0 has requirement ...
Looks like flake8 6.0.0 has no compatible ...
Read more >NuGet 6.0 Release Notes - Microsoft Learn
Summary: What's New in 6.0.0. This is the first release to offer full authoring and restoring support for NuGet packages targeting .
Read more >Changelog - Sphinx documentation
#10057: Failed to scan documents if the project is placed onto the root directory ... #9313: LaTeX: complex table with merged cells broken...
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 am afraid the change causes too much trouble. I changed the behaviour to the previous one. Released in 6.0.3
oh no… why is that a problem in your case? I could change it to the old version, but I thought it would be better when the types are dynamic props. Does it work when you define the
nodeTypesoutside of the component or wrapped in a useMemo so that the object does not change?