Add filter-count badge test for src/features/maintainers/components/pull-requests/PRFilterDropdown.tsx

[Jagadeeshftw]

📌 Description

src/features/maintainers/components/pull-requests/PRFilterDropdown.tsx (has a test file already) likely shows a badge/count of currently active filters on its trigger button. There's no test confirming that count stays accurate as filters are added/removed, which is an easy thing to get subtly wrong (off-by-one, stale count after a rapid toggle).

🧩 Requirements and context

• Add a test asserting the badge count matches the number of active filters after adding one, adding several, and removing one.
• Add a test that the badge is hidden (or shows 0/none) when no filters are active.
• Add a test for rapid toggle sequences not leaving a stale count.

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b test/pr-filter-dropdown-count-badge

2. Implement changes

• Modify: src/features/maintainers/components/pull-requests/PRFilterDropdown.test.tsx — add the count-accuracy cases.

3. Test and commit

• Run tests:

npm test -- run PRFilterDropdown

• Cover edge cases: zero active filters, one filter, many filters, rapid add/remove toggling.
• Include test output and details in the PR description.

Example commit message

test: add active-filter count badge accuracy coverage for PRFilterDropdown

✅ Acceptance criteria

• Badge count always matches the actual number of active filters across all tested sequences.
• Badge is hidden or shows a clear zero-state when nothing is active.
• Existing filter-application behavior (independent of the badge) is unaffected.

🔒 Security notes

None beyond standard correctness/regression risk.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[github-actions]

Assigned @dominiccreates to this issue via repo automation. Please open a PR referencing this issue (e.g. Closes #518) when you're ready.

[grantfox-oss]

🦊 GrantFox — @dominiccreates has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #518)
2. Your PR will be reviewed by the Grainlify maintainers

Good luck! Track your progress on GrantFox.

[Jagadeeshftw]

Unassigning @dominiccreates — this has been assigned for more than 2 days with no PR opened yet. No worries if you're still working on it, just re-comment and we'll happily reassign once you're ready to pick it back up.

[Jagadeeshftw]

Assigned @dominiccreates! Go ahead and open a PR referencing this issue (Closes #518) when ready. t.me/+vTbe0hOUKrFhNTJl

[Jagadeeshftw]

Tried to (re-)assign @dominiccreates but GitHub's API is silently rejecting it (201 response, empty assignees) even though the account exists — something changed on their end since the earlier successful assignment. Leaving unassigned for now.