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
Some notes on integrating the new template (theme) support from plotly/plotly.js#2761 (original discussion from #924). With just rerunning code generation, in plotly.py 3.1+ template support is already usable. For example:
Here are some of my thoughts for improving the integration for plotly.py users:
Write a custom validator for layout.template (right now it accepts anything and Plotly.js just ignores invalid properties)
Include some way to set a global template that is the default unless if it overridden in the constructor. Support saving this default to a ~/.plotly settings file.
Figure out what's going on with the new name and templateitemname properties that were added to all of the object array properties (e.g. annotations, images, etc.). I think the name properties should only show up in the template hierarchy and templateitemname should only show up in the normal object hiererahcy.
The text was updated successfully, but these errors were encountered:
Some notes on integrating the new template (theme) support from plotly/plotly.js#2761 (original discussion from #924). With just rerunning code generation, in plotly.py 3.1+ template support is already usable. For example:
Here are some of my thoughts for improving the integration for plotly.py users:
name
andtemplateitemname
properties that were added to all of the object array properties (e.g. annotations, images, etc.). I think thename
properties should only show up in the template hierarchy andtemplateitemname
should only show up in the normal object hiererahcy.The text was updated successfully, but these errors were encountered: