Problem with targetPath at nested branches

Question

Problem with targetPath at nested branches

schrodinger-cat opened this issue 4 years ago · 5 comments

I have strange targetPath in the store at drag event. You can see it here - https://codesandbox.io/s/hardcore-jackson-nr5xl?file=/src/App.vue

when I drop first element to second position I expect, that targetPath be [0, 1], but now it [0, 2]. in the DOM data-tree-node-path updated correctlly

Answer 1 · 2021-06-26T04:01:14.000Z

I just published 2.0.1-1.beta.3, please try.

Answer 2 · 2021-06-26T07:08:06.000Z

Sandbox cant load dependency, may be later. I cant try it right now at the normal enviroment, tommorow I will send you full feedback.

Anyway, thanks for your work.

Answer 3 · 2021-06-27T16:12:23.000Z

I tested 2.0.1-1.beta.3, and it work correct. Sometimes i catch issue, when oneMoveStore is empty (it returns {}), but i really dont know that is a bug or feature :) anyway in my case it dont really needed, i watch only prepend action, to send correct type to server

thank you

Answer 4 · 2021-06-28T00:41:43.000Z

oneMoveStore is for every move event. It is created when move start, destroied when move end. In event drag, it is destroied.

Answer 5 · 2021-11-03T12:05:49.000Z

This issue returned. I'm using version 2.0.10 and when i drag element after another in same branch - index of dragged element increased by 1. When i put dragged element before another - all fine.