Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Axis matching limitation
See original GitHub issueThis is a pretty problematic case for Plotly.py: https://codepen.io/nicolaskruchten/pen/ExaOMRr?editable=true
In this case, all axes have matches set to the first axis (x or y) but those axes have no traces, so no information is being shared among the axes that do have traces.
I’d be tempted to call this a bug… thoughts @alexcjohnson @archmoj ?
This is a problem for Plotly.py because make_subplots creates subplots and sets matches before knowing which subplots have traces.
Issue Analytics
- State:
- Created 4 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@etpinard My dev branch is at: https://github.com/plotly/plotly.js/commits/fix4501-match-axes_dev
Yes, the new minimal bug demo captures my intent here, thanks @archmoj 😃