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
The auto-generated type options mention a list of strings or datetimes is acceptable for parcoords -> dimensions -> values, however, as noted in the description the values must be a list of finite numbers (i.e. categorical options [strings / dates] are not possible).
The text was updated successfully, but these errors were encountered:
Wouldn't it be better to just implement support for strings and datetimes? I don't see a good reason to not support these data types in a parcoords plot.
I don't know much javascript, but I did play around with adapting plotly.express (the python API) to deal with these data types. That wasn't too hard, but involved the not-so-graceful approach of translating values to the supported datatypes and then manipulating the ticktext to emulate what real support would look like.
I could contribute this solution, but it feels like treating symptoms.
https://plot.ly/python/reference/#parcoords-dimensions-values
The auto-generated type options mention a list of strings or datetimes is acceptable for
parcoords -> dimensions -> values
, however, as noted in the description the values must be a list of finite numbers (i.e. categorical options [strings / dates] are not possible).The text was updated successfully, but these errors were encountered: