1. Fixed import paths:
- players.py: from .base → from ..services.base
- teams.py: from .base → from ..services.base
2. Added @classmethod decorators to PlayerService methods:
- get_players()
- search_players()
- get_player()
- update_player()
- patch_player()
- create_players()
- delete_player()
3. Updated all classmethods to use cls instead of self
Result: Router can now call service methods as static (PlayerService.get_players())
- Moved peewee/fastapi imports inside methods to enable testing without DB
- Added InMemoryQueryResult for mock-compatible filtering/sorting
- Updated interfaces with @runtime_checkable for isinstance() checks
- Fixed get_or_none() to accept keyword arguments
- _player_to_dict() now handles both dicts and Peewee models
Result: All 14 tests pass without database connection.
Service can now be fully tested with MockPlayerRepository.
- Removed direct Player model imports from service methods
- Added InMemoryQueryResult for mock-compatible filtering/sorting
- Added RealPlayerRepository for real DB operations
- Service now accepts AbstractPlayerRepository via constructor
- Filtering and sorting work with both mocks and real DB
- Tests can inject MockPlayerRepository for full test coverage
This enables true unit testing without database dependencies.
- Created ServiceConfig for dependency configuration
- Created Abstract interfaces (Protocols) for mocking
- Created MockPlayerRepository, MockTeamRepository, MockCacheService
- Refactored BaseService and PlayerService to accept injectable dependencies
- Added pytest configuration and unit tests
- Tests can run without real database (uses mocks)
Benefits:
- Unit tests run in seconds without DB
- Easy to swap implementations
- Clear separation of concerns
- Created BaseService with common patterns (cache, db, auth)
- Created PlayerService with CRUD, search, filtering
- Created TeamService with CRUD, roster management
- Refactored players.py router to use PlayerService (~60% shorter)
- Refactored teams.py router to use TeamService (~75% shorter)
Benefits:
- Business logic isolated in services
- Easy to unit test
- Consistent error handling
- Reusable across endpoints
