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

Improve the default number of ticks generated in continuous scales #929

Closed
markov00 opened this issue Dec 2, 2020 · 2 comments · Fixed by #1430
Closed

Improve the default number of ticks generated in continuous scales #929

markov00 opened this issue Dec 2, 2020 · 2 comments · Fixed by #1430
Labels
:axis Axis related issue enhancement New feature or request released on @38.1.x released Issue released publicly :xy Bar/Line/Area chart related

Comments

@markov00
Copy link
Member

markov00 commented Dec 2, 2020

Describe the solution you'd like
Extracted from elastic/kibana#84178

The amount of ticks in various time ranges selected are not pretty.
We previously made an effort in reducing the number of ticks.

100599292-1d541b80-3300-11eb-91b2-753841934283

Describe alternatives you've considered
We should better control and limit the number of tick labels generated

@markov00 markov00 added enhancement New feature or request :axis Axis related issue :xy Bar/Line/Area chart related labels Dec 2, 2020
@nickofthyme
Copy link
Collaborator

🎉 This issue has been resolved in version 38.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@nickofthyme nickofthyme added the released Issue released publicly label Oct 26, 2021
@nickofthyme
Copy link
Collaborator

🎉 This issue has been resolved in version 38.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:axis Axis related issue enhancement New feature or request released on @38.1.x released Issue released publicly :xy Bar/Line/Area chart related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants