Skip to content

feat: add 1d/2d/3d short time-range filters - #31

Open
RKdev wants to merge 1 commit into
nateherkai:mainfrom
RKdev:kz/short-time-ranges-and-pricing-update
Open

feat: add 1d/2d/3d short time-range filters#31
RKdev wants to merge 1 commit into
nateherkai:mainfrom
RKdev:kz/short-time-ranges-and-pricing-update

Conversation

@RKdev

@RKdev RKdev commented Jul 22, 2026

Copy link
Copy Markdown

Summary

  • Prepends 1d, 2d, and 3d range buttons to the Overview and Skills views, before the existing 7d/30d/90d/All options
  • No logic changes — same rolling-window calculation (Date.now() - days * 86400 * 1000), just shorter windows

Test plan

  • Visit Overview, confirm 1d/2d/3d buttons appear and filter data correctly
  • Visit Skills, confirm same
  • Confirm 7d/30d/90d/All still work as before

🤖 Generated with Claude Code

Prepend 1d, 2d, and 3d options to the RANGES array in the Overview and
Skills views, before the existing 7d/30d/90d/All buttons.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@RKdev

RKdev commented Jul 22, 2026

Copy link
Copy Markdown
Author

@nateherkai heads up on this PR when you get a chance!

muckybuzzwoo added a commit to muckybuzzwoo/token-dashboard that referenced this pull request Jul 22, 2026
Adds 1/2/3-day buttons to the Overview and Skills range selectors (upstream PR nateherkai#31). Fixes the position-based default (RANGES[1]) that would have shifted the default from 30d to 2d once the short ranges were prepended -- now looks up 30d by key.
@muckybuzzwoo

Copy link
Copy Markdown

Thanks — integrated the 1d/2d/3d range filters into my fork. Small heads-up: prepending the short ranges shifts the position-based default (RANGES[1]) from 30d to 2d, so I changed the default to look up 30d by key instead. Credit and notes here: https://github.com/muckybuzzwoo/token-dashboard/releases/tag/v0.6.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants