We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offending (?) line of code
plotly.js/src/traces/pie/defaults.js
Line 38 in 599dff9
This results in marker.colors being return by findArrayAttributes even though marker.colors is not in the user data. See https://codepen.io/bpostlethwaite/pen/dJozzo for an example.
marker.colors
findArrayAttributes
This is seemingly inconsistent with standard fullData behaviour.
The text was updated successfully, but these errors were encountered:
Possible other cases to worry about:
$ ag "dflt: \[\]" traces/sankey/attributes.js 103: dflt: [], 161: dflt: [], 198: dflt: [], 204: dflt: [], 209: dflt: [], traces/ohlc/attributes.js 67: dflt: [], 74: dflt: [], 81: dflt: [], 88: dflt: [], traces/parcoords/attributes.js 125: dflt: [], traces/table/attributes.js 72: dflt: [], 83: dflt: [], 152: dflt: [], 163: dflt: [], transforms/groupby.js 32: dflt: [],
A lot of these cases the trace wouldn't make sense without the attribute but... then what's the point of filling in an empty array?
Sorry, something went wrong.
Alternatively, maybe we should skip over empty arrays here.
skip over empty arrays
Worries me a bit, empty arrays can, in some cases, be different from non-arrays or missing values.
This appears fixed in 1.34.0 (most likely by the Plotly.react push)
1.34.0
Plotly.react
compared to in 1.33.1:
1.33.1
Closing.
No branches or pull requests
Offending (?) line of code
plotly.js/src/traces/pie/defaults.js
Line 38 in 599dff9
This results in
marker.colors
being return byfindArrayAttributes
even thoughmarker.colors
is not in the user data. See https://codepen.io/bpostlethwaite/pen/dJozzo for an example.This is seemingly inconsistent with standard fullData behaviour.
The text was updated successfully, but these errors were encountered: