How to update v-model in BaseTree

[thensanity]

`








<v-text-field
label="Search Contract"
v-model="search"
color="secondary"
hide-details
clearable
clear-icon="mdi-close-circle-outline"
@input="filterTreeData">

         <BaseTree ref="tree" 
         class="bgc-white mtl-tree" 
         v-model="filteredTreeData" 
         virtualization 
         :default-open="false"
         @open:node="fetchChildData">
  <template #default="{ node, stat }">
    <OpenIcon
       v-if="!node.isContractDate"
      :open="stat.open"
      class="mtl-mr"
       @click="stat.open = !stat.open"
        />

     <input
      class="mtl-checkbox mtl-mr"
      type="checkbox"
      v-model="stat.checked"
      v-if="node.isContractDate"
      @change="onSelected(node)"
    />
   
    {{ node.name }}
  </template>
</BaseTree>
       
    </div>
  </v-dialog>
  </v-col>
</v-row>

`

I have a BaseTree component with a v-model bound to filteredTreeData.
I'm facing an issue where, when I dynamically update the tree nodes bound to filteredTreeData through the open:node event, I can see filteredTreeData is updated with the new children of the node when it opens (as confirmed in the Dev Tools), and also vue watchers also showing filteredTreeData nodes is updated with new chidlren.
However, the UI does not reflect these updates immediately. The updated nodes only appear when the tree is re-initialized. What could be the issue here?

[phphe]

it only watch v-model object self's change.

[thensanity]

Are there any other ways to refresh the node so it shows its updated children when the open:node event triggers?

[phphe]

use inner methods to update node: https://hetree.phphe.com/v2/api#methods

[thensanity]

ok, thanks.

I just checked the documentation, but there are no update node methods available currently ?

The add method would not suffice as it will replace the whole state. All I want is to replace the existing children with new children.

[phphe]

you can record state in your node, then use https://hetree.phphe.com/v2/api#stathandler restore them when init the node

[thensanity]

ok, i got the idea how to handle all kind of situations, thanks for the help!