Propagate Plotly.js console errors to Python
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18.8k
- Forks
- 2.8k
- Avg merge
- 16h 26m
- Merged PRs (30d)
- 21
Description
Occasionally Plotly.js console errors are relevant to Python developers, for example in: https://github.com/plotly/plotly.js/issues/7289 where we show an error about a missing style.
For Python developers (especially in Jupyter) this is really gnarly to debug because they're never shown the issue unless they can figure out to check the console somehow.
I would wager there are a class of JS errors that we might not catch like this but I might be wrong. @alexcjohnson do you know if we have any handling in place for this kind of thing already?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing plotly.py and Jupyter integration for any handling of Plotly.js console errors. Reproduce the missing-style case described in Plotly.js issue #7289 and determine which JavaScript errors should be surfaced to Python; done means relevant errors are visible to Python developers without inspecting the browser console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- data-visualization, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100