You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using more than one column to define customdata, the data seems to be parsed as a tuple.
The example below shows three versions of the same figure:
LEFT. Only one column of customdata. Works as expected.
CENTER. Two columns of customdata. The first column in customdata is not parsed correctly when using a :.1s format. The second column in customdata is not parsed correctly by hovertemplate in go.Pie but is parsed correctly by texttemplate.
RIGHT. Workaround using customdata as a tuple and selecting its first %{customdata[0][0]} and second %{customdata[0][1]} values accordingly.
The text was updated successfully, but these errors were encountered:
gvwilson
changed the title
Bug report: customdata parsed incorrectly when array contains more than 1 column in piechart
customdata parsed incorrectly when array contains more than 1 column in piechart
May 20, 2025
When using more than one column to define
customdata
, the data seems to be parsed as a tuple.The example below shows three versions of the same figure:
customdata
. Works as expected.customdata
. The first column incustomdata
is not parsed correctly when using a:.1s
format. The second column incustomdata
is not parsed correctly byhovertemplate
ingo.Pie
but is parsed correctly bytexttemplate
.customdata
as a tuple and selecting its first%{customdata[0][0]}
and second%{customdata[0][1]}
values accordingly.Tested using:
Plotly.py: 6.0.1
Pandas: 2.1.4
The text was updated successfully, but these errors were encountered: