-
I updated yesterday from 2.1.0 to 3.3.1 but the customdata variable seems not to be working anymore.
is giving me a result like this:
Can anybody help? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Yes, that's a breaking change I didn't document because the default cases are covered by the new defaults. Sorry for that. You have two options:
customdata: $ex ys.map(()=>meta)
hovertemplate: >-
<b>%{customdata.friendly_name}</b><br><i>%{x}</i><br>
%{y:.1f}%{customdata.unit_of_measurement} <extra></extra>
hovertemplate: |
$ex `<b>${get(".name")}</b><br><i>%{x}</i><br>
%{y:.1f} ${get(".unit_of_measurement")}
<extra></extra>`
You can see how all the other defaults are defined here |
Beta Was this translation helpful? Give feedback.
Yes, that's a breaking change I didn't document because the default cases are covered by the new defaults. Sorry for that.
The reason behind the change is performance, this was using quite a bit of ram because the custom data needed to be replicated for each datapoint.
You have two options:
get(".name")
means "look at …