-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Access _fullLayout, _fullData and JS errors from Python #1967
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
@antoinerg heads-up! |
The JSON bit is going to be pretty awesome, based on Kaleido... basically something as simple as: import plotly.io as pio
import json
import plotly.graph_objects as go
def coerce(fig):
return go.Figure(json.loads(pio.kaleido.scope.transform(fig, format="json")), skip_invalid=True) |
Hi - we are trying to tidy up the stale issues and PRs in Plotly's public repositories so that we can focus on things that are still important to our community. Since this one has been sitting for several years, I'm going to close it; if it is still a concern, please add a comment letting us know what recent version of our software you've checked it with so that I can reopen it and add it to our backlog. Thanks for your help - @gvwilson |
Uh oh!
There was an error while loading. Please reload this page.
Just to record my pie-in-the-sky idea: if Orca had a mode where instead of returning an image, it returned a JSON object that contained
_fullLayout
,_fullData
and some warning objects, then we could make it much easier for users to understand the defaulting logic and various other-wise opaque error messages. From Python this could be accessed via a new renderer asfig.show("full_json")
or something?The text was updated successfully, but these errors were encountered: