Furthermore, it should be possible to move content to another shared type. This can be helpful when you want to move a type from one Y.Array to another.

🤯 Does this mean it will be able to resolve the parent-children loop?

For example, original content is

[
    {
      id: "A",
      children: [],
    },
    {
      id: "B",
      children: [],
    }
]

user0 and user1 concurrently move the content. user0 moved A inside B

[{
  id: "B",
  children: [
    {
      id: "A",
      children: [],
    },
  ]
}]

and user1 moved B inside A

[{
  id: "A",
  children: [
    {
      id: "B",
      children: [],
    },
  ]
}]

Hi Kevin, very exciting that "move" is on your radar! I understand you're focused on moving ranges within a Y.Array in this PR - is re-parenting ala https://discuss.yjs.dev/t/moving-elements-in-lists/92/14 in the realm of possibility at some point (I know, nobody likes dates, just in general :)).

Hi @marbemac,

That's a huge one.. It is definitely not in scope for the initial release. Eventually, yes, I'd like to support that. However, I feel there are more important things to work on right now, so I can't give a timeline.