Skip to content

feat(explore): filter issues by bounty range - #76

Closed
khongten124 wants to merge 1 commit into
zeemscript:mainfrom
khongten124:feat/filter-by-bounty-range
Closed

khongten124 wants to merge 1 commit into
zeemscript:mainfrom
khongten124:feat/filter-by-bounty-range

Conversation

@khongten124

Copy link
Copy Markdown

Summary

Closes #51

Acceptance Criteria Implemented:

  • Added a Bounty filter in the Explore page with options: Any, under 50, 50–50, over 50.
  • Accurately filters issues and combines seamlessly with existing complexity, language, and search filters.
  • Counts toward the active-filter badge count.
  • Cleared properly when clicking Reset.
  • Extended smoke test script in scripts/smoke-test.mjs to cover bounty range filtering.

Verification

  • Checked TypeScript types via tsc -b (clean typecheck).
  • Verified production build via vite build (clean build).

- Add Bounty filter with ranges: Any, under 50, 50–50, over 50
- Combine with complexity, language, and search filters
- Include bounty filter in active-filters badge count
- Support Reset to clear all active filters
- Update smoke test to verify bounty range filtering

Closes zeemscript#51
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.

Filter Explore issues by bounty range

1 participant