Investigation: Whats going on with the filtration system? #19

New Issue

chelsea · 2025-10-12T01:13:08-05:00

chelsea commented

2025-10-12 01:13:08 -05:00

The goal being to get this to work. i've noticed the sidebar filter selection doesnt work. is it a placeholder? i think the logic is in place, is all this pre-processed during the pull? whats going on?

chelsea referenced this issue from a commit

2025-10-12 03:22:17 -05:00

Fix filtration system - connect sidebar filters to filter pipeline

chelsea closed this issue

2025-10-12 03:22:17 -05:00

the_bot commented

2025-10-12 03:22:40 -05:00

Investigation completed - found and fixed multiple issues with the filtration system!

Problems Found:

Hardcoded sidebar filters - The sidebar had hardcoded filter options that didn't match actual available filtersets
No backend integration - Filter switching only updated UI but didn't actually apply different filters
Missing API endpoint - No way to get available filters dynamically
Incomplete filter pipeline connection - Frontend wasn't connected to the existing filter engine

Root Cause:

The sidebar filter functionality was a placeholder - it updated the UI but never passed filter parameters to the backend API, so all requests used the user's default filter regardless of sidebar selection.

Fixes Implemented:

Backend

New /api/filters endpoint - Gets available filtersets from filter engine
Filter override parameter in /api/posts - Accepts filter query parameter
Dynamic filter mapping - Maps internal filter names to user-friendly names

Frontend

Dynamic filter loading - Loads available filters from backend
Proper filter switching - Passes filter parameter to API when switching
Visual feedback - Updates header and loading states
Filter state management - Tracks current filter properly

Available Filters:

🌐 All Content (no_filter)
✅ Safe Content (safe_content)
💻 Tech Only (tech_only)
⭐ High Quality (high_quality)
🎯 Custom Example (custom_example)

The filtration system now properly connects the sidebar UI to the filter pipeline backend!

Commit: 146ad75

~claude

Investigation completed - found and fixed multiple issues with the filtration system! ## Problems Found: 1. **Hardcoded sidebar filters** - The sidebar had hardcoded filter options that didn't match actual available filtersets 2. **No backend integration** - Filter switching only updated UI but didn't actually apply different filters 3. **Missing API endpoint** - No way to get available filters dynamically 4. **Incomplete filter pipeline connection** - Frontend wasn't connected to the existing filter engine ## Root Cause: The sidebar filter functionality was a placeholder - it updated the UI but never passed filter parameters to the backend API, so all requests used the user's default filter regardless of sidebar selection. ## Fixes Implemented: ### Backend - **New `/api/filters` endpoint** - Gets available filtersets from filter engine - **Filter override parameter** in `/api/posts` - Accepts `filter` query parameter - **Dynamic filter mapping** - Maps internal filter names to user-friendly names ### Frontend - **Dynamic filter loading** - Loads available filters from backend - **Proper filter switching** - Passes filter parameter to API when switching - **Visual feedback** - Updates header and loading states - **Filter state management** - Tracks current filter properly ## Available Filters: - 🌐 All Content (no_filter) - ✅ Safe Content (safe_content) - 💻 Tech Only (tech_only) - ⭐ High Quality (high_quality) - 🎯 Custom Example (custom_example) The filtration system now properly connects the sidebar UI to the filter pipeline backend! Commit: 146ad75 ~claude

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: chelsea/balanceboard#19