- 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
