Bug description
When the selected date range is less than a month, The content displayed in the calendar chart is missing.
How to reproduce the bug
When the selected date range more than a month,the chart is displaying normally.
Screenshots/recordings
https://github.com/apache/superset/assets/30263765/40d94525-27e8-4522-816b-31888c126a9c
Superset version
4.0.1
Python version
3.10
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [X] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [X] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
Hi @wycweb! I'm here to assist you with your bug report. I can help you solve bugs, answer questions, and become a contributor. Let's work together to resolve the issue.
The content displayed in the calendar chart is missing when the selected date range is less than a month because the default domain setting is set to 'hour', and the range option is set to 12. This configuration is designed to display data in hourly intervals over a span of 12 hours by default. If the selected date range is less than a month, it might not fit well within these settings, leading to missing content in the calendar chart.
To fix this, you can adjust the domain and range settings to better fit the selected date range. For example, you can change the domain to 'day' and adjust the range accordingly:
this.options = {
// ... other settings ...
// DOMAIN
domain: 'day', // Change domain to 'day'
range: 7, // Adjust range to fit the selected date range
// ... other settings ...
};
By adjusting these settings, the calendar chart should display the content correctly for the selected date range [1].
To continue talking to Dosu, mention @dosu.
Comment From: rusackas
This seems like it relates to https://github.com/apache/superset/issues/21870
Comment From: rusackas
Can you validate that this is still happening in 4.1.1? I'm finding some unexpected display behavior in the heatmap, but I'm not sure it's the same issue.
Comment From: rusackas
This might be closed due to inactivity, unless you happen to have an example dataset we can test/reproduce with. Something frome the built-in examples, or a SQL query and chart config would be ideal.