What problem does this solve?
Currently, the monthly_summary() function is just a placeholder (pass). Users cannot view their monthly expense breakdown, which limits the usefulness of the expense tracker. Without this feature, there’s no way to analyze spending patterns or categories over time.
Proposed solution
Implement logic in monthly_summary() to:
Read expense entries from the CSV file.
Filter entries by the current month.
Aggregate totals by category.
Return or display a structured summary (e.g., dictionary, table, or formatted output).
Alternatives considered
No response
Which part of the app does this affect?
Testing
Estimated complexity
Medium (one function and one template change)
Before submitting
What problem does this solve?
Currently, the monthly_summary() function is just a placeholder (pass). Users cannot view their monthly expense breakdown, which limits the usefulness of the expense tracker. Without this feature, there’s no way to analyze spending patterns or categories over time.
Proposed solution
Implement logic in monthly_summary() to:
Read expense entries from the CSV file.
Filter entries by the current month.
Aggregate totals by category.
Return or display a structured summary (e.g., dictionary, table, or formatted output).
Alternatives considered
No response
Which part of the app does this affect?
Testing
Estimated complexity
Medium (one function and one template change)
Before submitting