-
Notifications
You must be signed in to change notification settings - Fork 633
Plotly.js 2.0 compatibility #1911
New issue
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
Comments
What are the newly suggested method(s) named? |
We're dropping Note that this state of affairs is what's been documented here https://plotly.com/javascript/plotlyjs-function-reference/ for a few years now, we're just finally getting around to dropping support for In terms of other things being dropped, I mostly have a list of what's being kept (in plotly/plotly.js#5395) but we should indeed assemble a full list of what's being dropped. I'll comment to that effect in plotly/plotly.js#5395. LMK if I can help you out with this transition @cpsievert! If you need dev bundles or you want to talk about this or whatever, I'm around to help. |
Any update on your end @cpsievert ? We're about to push a release candidate up to NPM which should help with testing and will give you a preview of the full change log :) |
This can be closed now that plotly.R 4.10.0 is released, or will more things change in the future? |
Hi there,
I lead the graphing libraries team at Plotly where we're busy working on version 2.0 of Plotly.js. I'm reaching out to folks who we know are "downstream" of Plotly.js to give you a heads-up about the changes so you can let me know if/how disruptive they're likely to be for you :)
Our approach here is not to make gratuitous breaking changes, but mostly to drop support for un/under-used functionality that slows down development for frequently-used functionality. We expect that the vast majority of users of Plotly.js and downstream systems like Plotly.py, Plotly.R, PlotlyJS.jl, Plotly.NET etc will be unaffected by these changes. The tracking issue we've got going is here plotly/plotly.js#5395
The major changes include, at the Javascript layer:
Promise
polyfill we're using, for security reasonsd3
modules underPlotly.d3
(so we can upgrade them internally)Plotly.plot
in favour ofPlotly.newPlot
andPlotly.react
The major changes at the schema layer:
pointcloud
,area
andcontourgl
traces, as well as the legacy polar attributes fromscatter
likescatter.r
andlayout.angularaxis
role
key from the schema altogetherI'm happy to answer any questions or consider changing our plans if it can avoid some major downstream disruption, so please get in touch or reply to this issue or to plotly/plotly.js#5395 :)
Nicolas
The text was updated successfully, but these errors were encountered: