Skip to content

fix(admin): persist dashboard date range in the URL - #2922

Merged
riderx merged 1 commit into
mainfrom
fix/admin-date-range-url
Aug 7, 2026
Merged

fix(admin): persist dashboard date range in the URL#2922
riderx merged 1 commit into
mainfrom
fix/admin-date-range-url

Conversation

@riderx

@riderx riderx commented Aug 7, 2026

Copy link
Copy Markdown
Member

Summary (AI generated)

  • Persist the admin dashboard timeframe in URL query params (range, plus start/end for custom)
  • Hydrate the admin store from the URL on load so reloads keep the selected period
  • Preserve query params when switching admin dashboard tabs

Motivation (AI generated)

Selecting a date range was lost on reload because it only lived in Pinia memory. Keeping it in the URL makes the current timeframe bookmarkable and stable across refreshes.

Business Impact (AI generated)

Faster admin workflows when reviewing users/orgs over a chosen window; shared links open on the same timeframe.

Test Plan (AI generated)

  • Open /admin/dashboard/users — URL gains ?range=30day (or current default)
  • Switch to 7 days — URL becomes ?range=7day
  • Reload the page — picker stays on 7 days and stats use that window
  • Pick a custom range — URL has range=custom&start=...&end=...; reload restores it
  • Switch admin tabs — range query is preserved
  • Open a URL with ?range=14day in a fresh session — page loads on 14 days

Generated with AI

Made with Cursor


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Review in cubic

Keep the selected timeframe across reloads and tab switches via range/start/end query params.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: ca529383-aaa3-4d93-b764-4c01735d17a9

📥 Commits

Reviewing files that changed from the base of the PR and between 4a50144 and 673becc.

📒 Files selected for processing (4)
  • src/components/admin/AdminFilterBar.vue
  • src/layouts/admin.vue
  • src/services/dateRange.ts
  • tests/date-range-query.unit.test.ts

Comment @coderabbitai help to get the list of available commands.

@cursor

cursor Bot commented Aug 7, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_2eb6a181-13eb-4d4b-8865-6825761e4312)

@codspeed-hq

codspeed-hq Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks1


Comparing fix/admin-date-range-url (673becc) with main (4a50144)

Open in CodSpeed

Footnotes

  1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@riderx
riderx merged commit b026fcd into main Aug 7, 2026
63 of 90 checks passed
@riderx
riderx deleted the fix/admin-date-range-url branch August 7, 2026 15:42
@sonarqubecloud

sonarqubecloud Bot commented Aug 7, 2026

Copy link
Copy Markdown

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.

1 participant