fix: fix uneven grid step across month boundary#563
Merged
Conversation
Contributor
|
Preview is ready. |
|
📖 Docs Preview is ready. |
|
Visual Tests Report is ready. |
korvin89
approved these changes
Apr 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the datetime axis auto-selects a 2-day tick interval, the grid spacing becomes uneven at month boundaries because d3's utcDay.every(2) resets its counter on the 1st of each month. In a 31-day month this produces a 1-day gap between the last day of the month and the 1st of the next.
Fix: use utcDay.filter() with an absolute Unix-day index so the 2-day cadence is preserved across month boundaries.