Hey @imaginativeone
, it shouldn't be. If you follow the same logic implemented here.
Every "piece" of your nested list that would allow an element to be dragged into, would be a DroppableItem with the proper events configured.
If you need something like being able to move a child node to another parent or sort the tree, the algorithm within the onDrop would be a little more complex than the example I've created for this article. But you would be able to do it.
Post here if you get anything new in regards to that. I would love to see how you solved the problem. :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey @imaginativeone , it shouldn't be. If you follow the same logic implemented here.
Every "piece" of your nested list that would allow an element to be dragged into, would be a
DroppableItemwith the proper events configured.If you need something like being able to move a child node to another parent or sort the tree, the algorithm within the
onDropwould be a little more complex than the example I've created for this article. But you would be able to do it.Post here if you get anything new in regards to that. I would love to see how you solved the problem. :)