Skip to content

style: refine leaderboard history filters with clear controls#125

Open
marktech0813 wants to merge 1 commit into
gittensor-agent-forge:mainfrom
marktech0813:style/leaderboard-clearable-filters-v2
Open

style: refine leaderboard history filters with clear controls#125
marktech0813 wants to merge 1 commit into
gittensor-agent-forge:mainfrom
marktech0813:style/leaderboard-clearable-filters-v2

Conversation

@marktech0813

Copy link
Copy Markdown

Summary

Makes the Resolved PR History filter/search controls recoverable: clear the search field, reset all filters in one click, and show a contextual empty state when a filter returns no matches.

Contribution Type

  • Leaderboard UI

Motivation

Once a reviewer types a search or picks a non-All filter that yields zero rows, the archive looks empty with no obvious way back. The prior empty copy always said "No Resolved PRs", which is misleading when the archive has entries that simply don't match the active controls.

Changes

  • Search field gains an inline clear (X) control when a query is present.
  • Active filter/search shows a Clear chip in the filter row and an aria-live match summary.
  • Empty state distinguishes "No Matching PRs" (filters active) from "No Resolved PRs", with a Clear filters action.
  • Touches only approved files: LeaderboardBoard.tsx, styles.css.

Testing

  • Manual testing
  • UI lint and build pass
  • CI passes

Visual Evidence

Leaderboard history filters with Clear controls and No Matching PRs empty state

Notes

Replacement for closed #122 / #123. GitHub will not reopen #122 after its branch was rewritten (force-push). Generation UI (#106) is out of scope for the active competition.

Made with Cursor

Add search clear, filter reset, live match summary, and a contextual
empty state so reviewers can escape empty filtered views quickly.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant