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
first of all, thank you for introducing template support to plotly.
As far as I understand, template settings should only "replace" default values but never overwrite explicit properties of a plot. However, when using colorscale in heatmaps, the colorscale is always overwritten by the template, no matter if it's specified by alias or as a list.
Glad you're enjoying templates and thanks for the report. It looks like the issue is that the templates set autocolorscale to True which overrides the explicit colorscale. It will take a little digging to figure out whether the issue is with the plotly.py template or with the plotly.js template engine.
In the meantime, you can set autocolorscale to False in your heatmap definition
Hi,
first of all, thank you for introducing template support to plotly.
As far as I understand, template settings should only "replace" default values but never overwrite explicit properties of a plot. However, when using
colorscale
in heatmaps, the colorscale is always overwritten by the template, no matter if it's specified by alias or as a list.Consider the following example:
In this case, the
ggplot2
theme's colorscale will be used rather the one explicitly specified in the trace.The text was updated successfully, but these errors were encountered: