Skip to content

fix: replace native filter dropdowns with compact HeroUI Select - #34

Merged
caigee-cmd merged 1 commit into
mainfrom
feature/heroui-filter-selects
Aug 29, 2026
Merged

caigee-cmd merged 1 commit into
mainfrom
feature/heroui-filter-selects

Conversation

@caigee-cmd

Copy link
Copy Markdown
Owner

Summary

  • Replace the five native <select> filters on Logs and Models with a shared HeroUI FilterSelect.
  • Keep the trigger at 32px / 12px type so it matches the toolbar Input and Button size="sm", not the 40px Access form selects.

Access account/model fields stay at h-10 because they sit in a labeled form. Logs/Models filters sit next to compact search fields and chip-sized button groups.

Test plan

  • rg '<select' frontend/src returns no native dropdowns
  • cd frontend && npm run lint
  • cd frontend && npm run sync
  • Open Logs: account / model / error-kind / runtime-account filters should match the 32px search field height
  • Open Models: provider filter should match the search field and refresh button

Logs and Models toolbar filters used native selects. Use a shared 32px
HeroUI Select so they match the compact toolbar instead of the 40px
Access form fields.
@caigee-cmd
caigee-cmd merged commit 43c759f into main Aug 29, 2026
6 checks passed
@caigee-cmd
caigee-cmd deleted the feature/heroui-filter-selects branch September 19, 2026 15:02
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