How to move TreeView nodes ???

[EpsilonYi]

when i move a node to another branch ,i got this warning.

[EpsilonYi]

https://play.vuetifyjs.com/#eNrNVL1u2zAQfpUrF9uAJMMyihaGZTRLn6BblEGQKYQo9QPypA6GtmzdChQoOrSPEHTomMeJk8fIkZISKn9IggxZJPK77777eDzpcMe0SucHVRU0NWcrtkaeVzJBvokLgHXjJ1Vll3aTlgUmouCqhyyIivNG8G+wEpSso5jZd8yuSUQbZKHxtSxxRbK82BJ3B4YN7YhudQVVcyEAg1BKvhV+Lopa+6lQqeR+WaMkVzEb0z+lUqRfKeE4KbaSf1FJoaemmgeoaj4b8zfreVfTtT0ftaODbk78hC6Eb7oNWSL16/XBQOMJMUg3QCMF2upUiQpBc6y7+RJ5VSqEHSieQQuZKnOY0ExODB2AdDXaHmmIDGd6eGNv5/pHgZKvIGb7/98vT38uYua54SaRNYUnyDUuJk6oddb3Cx7oLV3ng2rh89T2v04vfp+cn/04//dnf/J3+Yjy8n7lo9md3oRDc8Yx5+aJ0F++0J+F0jiDaDNYFBkFB/jatlUOrCHKdnZBJiRyNe1DGxvrie+iqDtDtyc7jljY51e1PrZu+nALnAbyVuWePJQecl9a+6HS5kWP9bwbTRpK1npsGbwPFh+YWXwMFiHz7Cfjjf6aHXZ0BfVnncA=

[EpsilonYi]

Vuetify error: Multiple nodes with the same ID
test1
test1
at <VListItemref=Refactive=undefinedactiveClass=undefined ...>
at <VTreeviewItemtitle="测试1"value="test1">
at <VTreeviewChildrendisabled=falseloadChildren=undefinedloadingIcon="$loading" ...>
at <VListChildrenitems=[object Object],[object Object],[object Object]returnObject=false>
at <VListref=Ref<[object Object]>baseColor=undefinedactiveColor=undefined ...>
at <VTreeviewitems=[object Object],[object Object],[object Object]>
at
at
at

[J-Sek]

This problem is a bit deep, relates to Vue rendering and is hard to fix without risking unintended performance degradation. You can track #20934 or give it a shot if you have some time.

The answer to the question in the title: check out new docs » second example for append & prepend slots here

[EpsilonYi]

There are another problem. the treeview can`t be search!

[J-Sek]

Not sure what you mean... There is an explicit example Search and filter in the docs.

Anyways, it would be best to consult your case on Discord instead of branching off the GitHub discussion that suppose to be focused on a different feature.

[EpsilonYi]

https://play.vuetifyjs.com/#eNrNVbGO00AQ/ZVhmySS7SiJEChKIq6hpaGLUxh7TFa3cazdtQFF6a6jQ0JCFPAJJwpKPucCn8F47U3WOd+dTqIgRbz7ZubN27fjZLljSsbDizwPygLZlM00bnIRaVyEGcCs9KM8N0uzibeZjniGsoEMqCViyfGdhQCmnFjUPGTmGbJTpAL8S/xAsTISBd6KGbQrGsWal5GO3gi04FEEybCyofSV2OopycYsIaKd4YV9yJx0o5vTaVyIFBBCJZuE+xueFcqPuYwF+ttCCzq1K6f6vIgFjy+pYB1licDXMspUv+rmgZYFDtr5i9mw7unKHrbsrqGTo10un5k7bp3rf7MhjYT6dz5UUHsCK6Qe0BYDbVUsea5BoS7q+eWbfCs17EBiCntI5XYDPZr5XpUOQLxKG48UzKuc/vIkb+fq11wLnELIDj8//rn+PAqZ54bN4E6hp1HpUc8J7Z11N+GFSug672QbP47t8OX699erm1+fbn58O1x9n9zDPOlmXg1ueTO25rRjzs1TQnP5XL3kUukBzBdWIk8paOGjbMMcGEGBymmY0DBYiGcJvn+VGmzgwYg6N3Vp/4mbKDB7q9eDkx1OkGQVxJPS6CQ2vneI6tPVuY40S9JEgrxQ61rIkQSQZvzOCuq7rPars6bnZa0urgkWe9gFm9nYcJ+kLitOfPUFNsZ18DzaiwesqB70NRvWLy29rmzvsUnwNBg9Y9XieTAaM8/8mHit/6saW/0Fy48JWw==

[EpsilonYi]

try this,why it still show this problem?

[J-Sek]

Annoying, yes. But still just a warning. The team has it near the top of the priority list, but it is not that simple - relates to Vue rendering optimization.