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.
[3.0.0-alpha] Incorrect behavior when forcing time unit to month
See original GitHub issueExpected Behavior
Using unit: 'month' for time axis should be ok whatever the data.
Current Behavior
If the intervals between data points are too short, using unit: 'month' leads to unusable chart.
Steps to Reproduce (for bugs)
Fiddle that reproduces the issue: https://jsfiddle.net/7ce1afx4/
If we remove unit: 'month', the issue is gone.
If in generateDate we add “* 30” to generate monthly points instead of daily points, the issue is gone too.
Context
I encountered this issue after migrating to 3.0.0-alpha, I think this is a regression because I never saw this with 2.9.
Environment
- Chart.js version: 3.0.0-alpha
- Browser name and version: Chromium 80
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 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
I want to thanks you and all the Chart.js maintainers for your great work, this alpha fixes many long standing bugs I had with 2.x and already seems pretty stable!
I sent a fix here that makes your sample work: https://github.com/chartjs/Chart.js/pull/7211
Thanks for the bug report and trying out the alpha!