Tree and data must be overridden in order to update the chart

[stockiNail]

Going to the last version, I have discovered that if you change the values of the tree (or data) without instantiating new object (or array), the chart will not be updated.

This is because the tree is stored in the controller and checked with new one at every update:

chartjs-chart-treemap/src/controller.js

Line 112 in f6a7af1

if (this._rectChanged || this._key !== key || arrayNotEqual(this._groups, groups) || this._prevTree !== tree) {

Maybe it's implemented as designed. But maybe it could be better to check not the instance but the content of the tree.

[kurkle]

If I remember correctly, arrayNotEqual did not work previously, so this check was always true.
That is how it was designed. If you share the use case, maybe we can figure out if we can improve things.

[stockiNail]

I don't have a real use case but in my showcase, I'm allowing the user to "randomize" the data and I didn't create new object but only change the existing one.
I think the check is not related to arrayNotEqual (because a tree could be also an object) but is related to this._prevTree !== tree.
But if it is as designed, no need to change it, if we will not be a specific case. It sounds to me a deviation of the "normal" way how CHART.JS can update the chart.

[kurkle]

Sounds like the desing is bad. It never worked as designed in previous versions, so it could also be considered a bug :)

[stockiNail]

oki! let me copy the discussion to an issue, for tracking