plotly / plotly/angular-plotly.js
Autorange does not work with type bar with range slider?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 81
- Avg merge
- 8h 48m
- Merged PRs (30d)
- 18
Description
There was an older issue posting related to this that hasn't had any activity and after checking the plotlyjs issue page, i am confused as I cannot tell if autorange is behaving as i am understanding it.
e.g.:
https://community.plotly.com/t/plotly-autorescaling-y-axis-range-when-range-slider-used/73970
https://codepen.io/niwsa/details/BXBjQQ
https://community.plotly.com/t/update-y-axis-domain-when-zoomed-on-x-axis/2073
https://github.com/plotly/plotly.R/issues/912
https://github.com/plotly/plotly.js/issues/1876
some replies had mentioned to just 'filter' the data using relayout event but i'm not sure how this can be done with those range values or how that will impact the range slider 'sub chart' image if you end up 'filtering' and removing the rest of the bars.
in my https://stackblitz.com/~/github.com/ysk3a/angular16plotly , if you slide the range to show the smaller bars, the y-axis does not 'auto range' for the bars to be visible.
i'm not sure if this is a bug, maybe caused by me missing property in my config, a wip feature in the plotly library that plotly is trying to add or autorange is working as intended.
i'm working with angular 16 and "angular-plotly.js": "^5.2.2", "plotly.js-dist-min": "^2.27.1",
Contributor guide
No contributing guide indexed for this repository
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 reproducing the behavior in the linked Angular 16 StackBlitz using angular-plotly.js 5.2.2 and plotly.js-dist-min 2.27.1. Compare the y-axis autorange when the range slider is moved to show smaller bars, and review the linked Plotly discussions and issues. Done means identifying whether this is a configuration issue, an angular-plotly.js issue, or expected Plotly behavior, with a clear minimal reproduction or explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- data-visualization, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100