possible one-off bug in moving a node

[sdavey]

it looks like there may be a one-off bug when dragging and dropping in a subtree. I made the following change to the first line of getChildIndex(): let index = parent.data.parent ? -1 : 0 without that change the new position in the parent is one higher than it should be because when looping through the parent's children, the first node is the "tree-content" node.

[MattPurland]

So that's what's happening. Looks like I'll be forking/patching this then