Align dashboard trend dates with Vercel - #30
Merged
Conversation
Expand multi-day presets to the local calendar days touched by the rolling selection and use daily trend buckets for short multi-day ranges. Canonicalize existing shared URLs and keep the date picker end date inclusive.
Keep multi-day presets on the client-local hour boundaries Vercel requests while using daily trend granularity. Add frontend and upstream-query regressions for the Jul 13 through Jul 20 window.
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
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.
Summary
Known API limitation
The public aggregate endpoint has no timezone parameter, so daily values are UTC-bucketed and may differ from Vercel's private timezone-aware dashboard. The requested Jul 13 through Jul 20 window is still sent unchanged and returns eight supported-API date buckets; no points are hidden or relabelled.
Verification