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
Currently, The (single) GenericChart type is a tuple of data, layout, and config. Different endpoints such as the Dash Graph component or Kaleido that accept plotly graphs in JSON format however expect these to be fields of the same object, e.g.
{
"data" : ... , "layout": ..., "config": ...
}
or at least
{
"data" : ... , "layout": ...,
}
with the config object being separate
We should adapt the type accordingly, either by making both Union cases of GenericChart inherit from DynObj or abstracting Chart/MultiChart as record types. Additionally, we should adapt the html scaffold for displaying Charts to render plotly graphs directly from that Json instead of declaring data/layout/config objects in a script tag.
The text was updated successfully, but these errors were encountered:
Reference docs from plotly.py specifies the top level fields of the figure object as data, layout, and frames. As frames is needed for animations, which are currently not supported by this library, the first step is supporting data and layout and omitting frames until animations are supported.
Description
Currently, The (single)
GenericChart
type is a tuple ofdata
,layout
, andconfig
. Different endpoints such as the DashGraph
component or Kaleido that accept plotly graphs in JSON format however expect these to be fields of the same object, e.g.or at least
with the config object being separate
We should adapt the type accordingly, either by making both Union cases of
GenericChart
inherit fromDynObj
or abstracting Chart/MultiChart as record types. Additionally, we should adapt the html scaffold for displaying Charts to render plotly graphs directly from that Json instead of declaring data/layout/config objects in a script tag.The text was updated successfully, but these errors were encountered: