From 20e79b704f757a548219c746754e44c83783693b Mon Sep 17 00:00:00 2001 From: Trey t Date: Tue, 23 Dec 2025 17:51:06 -0600 Subject: [PATCH] Fix widget overdue count to use kanban categorization MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The widget was calculating overdue count from due dates, which didn't account for in-progress tasks. Now uses the isOverdue flag from kanban categorization, ensuring the count matches the displayed tasks. Before: 3 overdue (date-based calc included in-progress tasks) After: 2 overdue (matches kanban which excludes in-progress) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- iosApp/Casera/MyCrib.swift | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/iosApp/Casera/MyCrib.swift b/iosApp/Casera/MyCrib.swift index b2f8fd8..5f50178 100644 --- a/iosApp/Casera/MyCrib.swift +++ b/iosApp/Casera/MyCrib.swift @@ -210,9 +210,10 @@ struct SimpleEntry: TimelineEntry { return TaskStatsCalculator.calculate(from: dueDates) } - /// Overdue tasks count + /// Overdue tasks count - uses the isOverdue flag from kanban categorization + /// which correctly excludes in-progress tasks var overdueCount: Int { - calculatedStats.overdueCount + upcomingTasks.filter { $0.isOverdue }.count } /// Tasks due within the next 7 days (exclusive of overdue)