Skip to content

Consider the list filter criteria in the widget configuration - #132

Open
patrickunterwegs wants to merge 1 commit into
mainfrom
claude/widget-config-filter-criteria-mietlt
Open

Consider the list filter criteria in the widget configuration#132
patrickunterwegs wants to merge 1 commit into
mainfrom
claude/widget-config-filter-criteria-mietlt

Conversation

@patrickunterwegs

Copy link
Copy Markdown
Member

The widget so far showed every entry of the configured calendar. It now
offers the same filter criteria as the list top bar (hide completed
tasks, category, status), stored per widget in the Glance state and
applied when the entries are loaded.

To share the filtering itself instead of reimplementing it for the
widget, the per-entry check moved into ListFilterCriteria.matches(),
which ListState now uses as well. ListFilterRow reports back a changed
ListFilterCriteria rather than a ListAction, so it can be reused outside
of the list screen, and its "Hide completed tasks" label became a string
resource.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01RwavgpN8tKbJS7998Ecn6z

The widget so far showed every entry of the configured calendar. It now
offers the same filter criteria as the list top bar (hide completed
tasks, category, status), stored per widget in the Glance state and
applied when the entries are loaded.

To share the filtering itself instead of reimplementing it for the
widget, the per-entry check moved into ListFilterCriteria.matches(),
which ListState now uses as well. ListFilterRow reports back a changed
ListFilterCriteria rather than a ListAction, so it can be reused outside
of the list screen, and its "Hide completed tasks" label became a string
resource.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RwavgpN8tKbJS7998Ecn6z
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.

2 participants