Skip to content
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

elasticChartsCrosshair is not positioned correctly for some intervals #195

Closed
alexwizp opened this issue Apr 25, 2019 · 1 comment · Fixed by #200
Closed

elasticChartsCrosshair is not positioned correctly for some intervals #195

alexwizp opened this issue Apr 25, 2019 · 1 comment · Fixed by #200
Assignees
Labels
bug Something isn't working released Issue released publicly

Comments

@alexwizp
Copy link
Contributor

Describe the bug
elasticChartsCrosshair is not positioned correctly for some intervals

In my example: timeFrame: 1week, interval: 12h

Screenshots
chart_issue_1

@alexwizp alexwizp added the bug Something isn't working label Apr 25, 2019
markov00 added a commit that referenced this issue May 2, 2019
Use a d3 bisect function on invertWithStep instead of relying on the minInterval and bandwidth values. This enables the use of irregular intervals as dataset for linear/time x axis

fix #195, fix #183
markov00 pushed a commit that referenced this issue May 2, 2019
## [4.0.1](v4.0.0...v4.0.1) (2019-05-02)

### Bug Fixes

* **scales:** use bisect to handle invertWithStep ([#200](#200)) ([f971d05](f971d05)), closes [#195](#195) [#183](#183)
@markov00
Copy link
Member

markov00 commented May 2, 2019

🎉 This issue has been resolved in version 4.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@markov00 markov00 added the released Issue released publicly label May 2, 2019
AMoo-Miki pushed a commit to AMoo-Miki/OpenSearch-Dashboards that referenced this issue Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released Issue released publicly
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants