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.
Fix x-axis tick alignment
Fixes #3483. The underlying issue was that some x-axis ticks would end up in the wrong position, overlapping in some cases and being deleted by the code to ensure ticks don't overlap. This seems to be because the first tick on the x-axis has its position adjusted in two places: first by setting and adjusting
firstTickPosition
according toremainingMins
on line 620, and then again inside the loop - which I remove in this change.I've also added a unit test which fails under the old code. This test makes sure that the
generateHourScale
function generates x axis ticks which do not overlap under the conditions seen in #3483.Before:
After:
Type of change
Please delete options that are not relevant.
Checklist:
- [ ] I have commented my code, particularly in hard-to-understand areas- no comments needed for this change IMO, happy to add some if requested