Closed andreroggeri closed 5 years ago
Welcome and thanks for the thorough bug report!
Good catch 👍 fixed with 2.0.0-rc.7
Great! 😁 Any chance of this being ported to 1.x.x versions?
I can't use alpha/beta/RC packages on my company 😔
Sure, v1.1.1 it is 😃
But you can use v2.0.0 as well because it's out now as stable.
Describe the bug If the directive is destroyed before the dragend event, it stays on a invalid state. For example, anything can be dragged to a dropzone because the current state is still dragging. I believe that calling the
endDrag
method on destroy should fix this issue To Reproduce If possible please provide a StackBlitz based on this template https://stackblitz.com/edit/ngx-drag-drop-destroy-cleanup?file=src/app/app.component.htmlSteps to reproduce the behavior:
Expected behavior It should not allow to drag elements that are not draggable (Only in case of dndAllowExternal=true) and no error should occur on console Screenshots
If applicable, add screenshots to help explain your problem.Desktop (please complete the following information):