feat(dashboards): Improve TimeSeriesVisualization X axis label selection and rendering
#85409
Conversation
This file contains 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
github-actions
bot
added
the
Scope: Frontend
narsaynorath
approved these changes
Feb 19, 2025
armenzg
pushed a commit
that referenced
this pull request
Feb 19, 2025
…ction and rendering (#85409) The current setup has a few downsides: - too many tick labels. There are lots of labels, they're very busy and take up a lot of screen - redundant labels. Every label has the time and date, even when looking at 60 days when the time isn't relevant This PR uses a different approach, called a "cascading" formatter. The code explains in detail what's happening, but I think the results are better shown using screenshots. The end result is nice single-line labels, no overlap, sparse axes, and simple behaviour.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current setup has a few downsides:
This PR uses a different approach, called a "cascading" formatter. The code explains in detail what's happening, but I think the results are better shown using screenshots.
The end result is nice single-line labels, no overlap, sparse axes, and simple behaviour.
e.g.,
