Skip to content

Show active-filter state and quick-clear in schedule header#259

Merged
JacobCoffee merged 1 commit intomainfrom
fix/filter-active-indicator
Apr 18, 2026
Merged

Show active-filter state and quick-clear in schedule header#259
JacobCoffee merged 1 commit intomainfrom
fix/filter-active-indicator

Conversation

@JacobCoffee
Copy link
Copy Markdown
Member

Summary

  • When track filters are active (`excludeTracks` non-empty), the funnel icon in the schedule header switches from outline → filled and turns PyCon 2026 pink (#DD04D2).
  • A `close-circle` button appears before the funnel; tap clears all filter state (in-memory, storage, schedule refresh) in one shot.
  • No header change at all when no filters are active.

Addresses the "I have everything unselected except one track and I can't tell filters are on" confusion + "I can't quickly reset filters" friction.

Test plan

  • No filters applied → header looks identical to before (outline funnel, gray)
  • Open filter modal, exclude a track, confirm → funnel fills + goes pink, close-circle button appears
  • Tap close-circle button → all filters cleared, icons return to default, schedule shows all tracks again
  • Re-open the app → cleared state persists (storage was updated)
  • Reopen filter modal → all tracks shown as included

When track filters are active (excludeTracks is non-empty):
- Funnel icon switches from outline to filled and turns PyCon 2026 pink
- A close button appears before the funnel; tap clears filters (state,
  persisted storage, and re-runs the schedule query)

Before, there was no visual cue that filters were active, and clearing
required opening the filter modal and toggling each track back on.
@JacobCoffee JacobCoffee merged commit cfaa2ac into main Apr 18, 2026
2 checks passed
@JacobCoffee JacobCoffee deleted the fix/filter-active-indicator branch April 18, 2026 05:16
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