moveNode.ts doesn't properly handle the case when the origin and the target of the move operation are under the same parent and the target node is being moved forward to a later position under the parent.
Interesting find - happy to look into this in about a week. Super swamped at the moment. Glad to release a new version sooner if you put in a PR with a fix!
moveNode.ts
doesn't properly handle the case when the origin and the target of the move operation are under the same parent and the target node is being moved forward to a later position under the parent.Repro: