No dropzone exists in clone use case when data source is an ng-repeat and not fixed object

Question

No dropzone exists in clone use case when data source is an ng-repeat and not fixed object

JakeMauch opened this issue 7 years ago · 4 comments

So most of the examples we use are fixed, hardcoded objects. My data consists of a variable number of ui-sortable lists which must be able to clone to a single ui-sortable. Currently, in the clone use case, attempting to drag from one of these other ui-sortables into the target will render a dropzone of undefined and as a result fail to move anything properly.

Sorry if I fail to tag this properly, not the most experienced with github's issue tracker.

Answer 1 · 2017-05-19T07:53:29.000Z

Hi there!
Can you fork one of the examples found in README and post it to showcase you use case?

Answer 2 · 2017-05-28T20:13:35.000Z

Any feedback on this?

Answer 3 · 2017-05-29T07:19:31.000Z

Sorry, I'll try to get some data soon but I've been forced to move on in my project

…

On May 28, 2017 4:13 PM, "Thodoris Greasidis" ***@***.***> wrote: Any feedback on this? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#519 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AauxE_22VkRPJ-cG8_KuLcew6XZ3fjb3ks5r-dVxgaJpZM4NfNug> .

Answer 4 · 2017-07-01T13:28:11.000Z

Updated the cloning example found in README to work with a dynamic number of sources.
Closing for now, feel free to re-open in any case.