Prevent reevaluating of table bindings when location of node is modified


I have modified the Add or Remove Columns example and added a two-way binding on the node location:

Now, whenever the node is being moved, some bindings of the table are reevaluted (see the console logs).

Is this unavoidable or how could I prevent the frequent reevlautions of the bindings? Now sure how this affects the performance but if there is an easy solution for this I’d like to avoid the revaluations.

I doubt there is anything that you can do, but I will look into the behavior to see if it can be optimized without breaking existing apps.