[REFACT]: Implement Modular Class Structure for User Data and Integration #90
Description
Refactor: Implement Modular Class Structure for User Data and Integration
📝 Description
Refactor the system to use distinct classes for different user-related data, mapping relationships between them with IDs. Integrate these classes seamlessly with leaderboards and profiles. Provide separate functions to fetch and manipulate different data aspects for better modularity and maintainability.
✅ Features to Include
- Create separate classes for:
- User Profile (basic info, socials, bio, password)
- Elo Rating History (time series data for elo changes)
- Match Stats (wins, losses, draws, scores)
- Achievements and Badges
- Debate History (individual debates with opponents and outcomes)
- Map relationships between classes using unique IDs (e.g., userId, matchId)
- Integrate these classes with:
- Leaderboard system (fetch and update user rankings)
- Profile pages (display comprehensive user info and stats)
- Develop distinct functions/APIs for:
- Fetching user profile data
- Retrieving elo rating trends
- Getting match statistics summary
- Listing recent debates
- Loading user achievements
- Ensure separation of concerns to improve code readability and extensibility
- Optimize data fetching for performance (e.g., lazy loading, pagination)
- Write unit tests for class methods and API endpoints