Fixed get_chore_with_assignments() to include assignment_type in dict.
This resolves the ResponseValidationError where assignment_type was
missing from API responses despite being present in the database.
- NEW: ChoreAssignmentType enum (ANY_ONE, ALL_ASSIGNED)
- NEW: assignment_type field with default ANY_ONE
- ANY_ONE: Only one assigned person needs to complete
- ALL_ASSIGNED: All assigned people must complete
- Supports new chore completion logic for multi-user assignments
- Creates migration 004_add_assignment_type.py
- Adds assignment_type VARCHAR(20) to chores table
- Default value: 'any_one' for backward compatibility
- Values: 'any_one' (only one needs to complete) or 'all_assigned' (all must complete)
- Safe to run on existing database
When updating a chore with an empty due_date field, SQLite was throwing an error
because it only accepts Python datetime and date objects, not empty strings.
This fix checks if due_date is an empty string and converts it to None before
setting the attribute, preventing the TypeError.
Error fixed: "SQLite DateTime type only accepts Python datetime and date objects as input"
- Changed imports to use app.core.database and app.models structure
- Added Base import from app.core.database (not app.models)
- Fixed imports to match actual project structure
- Added comprehensive demo data with 5 users and 12 chores
- Fixes ModuleNotFoundError when running database initialization
- Added ENVIRONMENT field (str, default: "development") to match .env file
- Renamed ALLOWED_ORIGINS to CORS_ORIGINS to match .env file
- Updated cors_origins property to use CORS_ORIGINS instead of ALLOWED_ORIGINS
- Fixes Pydantic validation error when loading settings from .env