Fix widget overdue count to use kanban categorization
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 <noreply@anthropic.com>
This commit is contained in:
@@ -210,9 +210,10 @@ struct SimpleEntry: TimelineEntry {
|
|||||||
return TaskStatsCalculator.calculate(from: dueDates)
|
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 {
|
var overdueCount: Int {
|
||||||
calculatedStats.overdueCount
|
upcomingTasks.filter { $0.isOverdue }.count
|
||||||
}
|
}
|
||||||
|
|
||||||
/// Tasks due within the next 7 days (exclusive of overdue)
|
/// Tasks due within the next 7 days (exclusive of overdue)
|
||||||
|
|||||||
Reference in New Issue
Block a user