Repository navigation
Error when dropping an item with nested list into a another item with nested list #44
Description
Activity
A bit of debugging showed that the reason is that during
onAddmethod theng-sortablewill the dragged item from the list and call the$scope.apply()which will trigger the$destroyon theng-sortable.Removing that
$scope.apply()is however not enough because there's another one that's called also to early.However, removing both of those actually removes the above reported error and on the first glance all seems to work fine.
So now the question remains why was there a need to trigger the digest twice in
onAdd(once through_syncand once directly) and in onceonUpdate(through_sync).Isn't it enough to just call
scope.$apply()inonEnd?
Consider the following case:
If both the main list and sublists are connected then root
itemscan be normally sorted each other anditem 2can be dragged to subitem ofitem 1oritem 3.However, if you drag
item 3as subitem ofitem 1, i.e. aiming to get the following:then there will be the following error (and the
subitem 2will not be shown):A bit of debugging showed that
ng-sortabletriggers destroy which deletes, I believe, the sortable of the dragging item i.e.item 3.Here is a minimal codepen demo.
This might be related to #43