Skip to content

[US-7.1 / OBT-210] Add a reusable FilterBar component - #20

Open
levigtri wants to merge 2 commits into
mainfrom
levigft/obt-210-us-71-a-reusable-well-designed-filter-bar-component
Open

[US-7.1 / OBT-210] Add a reusable FilterBar component#20
levigtri wants to merge 2 commits into
mainfrom
levigft/obt-210-us-71-a-reusable-well-designed-filter-bar-component

Conversation

@levigtri

@levigtri levigtri commented Jul 5, 2026

Copy link
Copy Markdown
Member

Summary

US-7.1 / OBT-210 — Add a reusable, well-designed FilterBar component so filtering across the console is consistent and polished instead of ad-hoc per page. Unblocks US-7.2 (Users) and US-7.3 (Access Requests).

Changes

  1. New src/components/common/FilterBar.tsx:
    • filters prop — array of configs (key, label, options, value, onChange, optional placeholder/inactiveValue/className).
    • optional search prop (value, onChange, placeholder).
    • optional resultLabel (e.g. "12 results").
    • active filters (value ≠ inactiveValue, default "all") are highlighted with the telha accent; the standalone Filter icon is dropped to reduce visual noise.
    • styled with Shema tokens (areia/surface/telha).

Type of Change

  • Feature

Testing

  • npm run typecheck — pass
  • npm run lint — 0 errors (pre-existing ProjectsPage warning only)
  • npm run build — pass

Front-only. Wiring into the Users page (US-7.2) and Access Requests (US-7.3) is stacked on top of this branch.

Introduce a shared FilterBar with configurable filter dropdowns (label, options,
value, change handler), an optional search input, and an optional result label.
Active filters are highlighted with the telha accent, and the standalone Filter
icon is dropped to reduce visual noise. Styled with the Shema design tokens.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@levigtri, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 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: QUIET

Plan: Pro Plus

Run ID: bc575307-e7ad-4c9b-b86a-01658a21f72e

📥 Commits

Reviewing files that changed from the base of the PR and between 130fc4a and e819be0.

📒 Files selected for processing (1)
  • src/components/common/FilterBar.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch levigft/obt-210-us-71-a-reusable-well-designed-filter-bar-component

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

@levigtri levigtri self-assigned this Jul 15, 2026
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