Change tree model so it does not directly modify the user's model about vue-tree HOT 1 CLOSED

Okay, so that original plan won't really work. It separates things out within the component, but a whole bunch of traversal and processing is done based on the model itself. Kind of makes sense when consider how tightly integrated tree nodes are with the tree and the parent/sub nodes. Instead, the plan is to encapsulate anything tree-related within a fairly specific property added to/specified on the models.

Why even do this instead of declaring the required properties on a node model and be done with it? Because hierarchical data is everywhere, and it can be an absolute pain to have to massage that data into the tree's desired format. If instead you can just have one node (named in a way that collisions are very unlikely) then it makes using your own data without change that much easier.

from vue-tree.