How chetan-1-hash/criclively works
CricLively is a cricket tournament and match-management application: users register and manage profiles, organizers configure tournaments, teams, and matches, scorers record ball-by-ball play, and users view match and tournament information. The frontend routes these experiences and shares an HTTP client; the backend exposes REST controllers, applies domain services, and persists application data through repositories. The excerpts establish player/profile and scoring paths particularly well; several other capabilities are visible in the route tree but their internal calls were not sampled, so those links are omitted.
Main entry points: App.tsx Application routes · ProfileService.java Profile service · ScoringService.java Scoring rules · PlayerService.java Player service
Components 26
Web application
- Application routes
Frontend/CricLively/src/App.tsx - HTTP client
Frontend/CricLively/src/API/client.ts - Profile experiences
Frontend/CricLively/src/components/ProfilePage.tsx - Match experiences
Frontend/CricLively/src/components/Matches.tsx - Tournament dashboard
Frontend/CricLively/src/components/DashboardTournament.tsx - Scorer interface
Frontend/CricLively/src/components/Scorer.tsx - Score viewer
Frontend/CricLively/src/components/viewer.tsx
Identity and players
- Player endpoints
Backend/CricLively/src/main/java/com/CricLively/RestController/PlayerController.java - Profile endpoints
Backend/CricLively/src/main/java/com/CricLively/RestController/ProfileController.java - Profile service
Backend/CricLively/src/main/java/com/CricLively/Service/ProfileService.java - Player service
Backend/CricLively/src/main/java/com/CricLively/Service/PlayerService.java - Player records
Backend/CricLively/src/main/java/com/CricLively/Entities/Player.java - Profile list DTO
Backend/CricLively/src/main/java/com/CricLively/DTO/ProfileList.java - Account roles
Backend/CricLively/src/main/java/com/CricLively/Entities/Enums/Role.java
Competition management
- Match service
Backend/CricLively/src/main/java/com/CricLively/Service/MatchService.java
Live scoring
- Scoring endpoints
Backend/CricLively/src/main/java/com/CricLively/RestController/ScoringController.java - Scoring rules
Backend/CricLively/src/main/java/com/CricLively/Service/ScoringService.java
Persistence
- Player repository
Backend/CricLively/src/main/java/com/CricLively/Repository/PlayerRepository.java - Profile repository
Backend/CricLively/src/main/java/com/CricLively/Repository/ProfileRepository.java - Image storage
Backend/CricLively/src/main/java/com/CricLively/Service/ImageStorageService.java - Team repository
Backend/CricLively/src/main/java/com/CricLively/Repository/TeamRepository.java - Tournament repository
Backend/CricLively/src/main/java/com/CricLively/Repository/TournamentRepository.java - Ball repository
Backend/CricLively/src/main/java/com/CricLively/Repository/BallByBallRepository.java - Match repository
Backend/CricLively/src/main/java/com/CricLively/Repository/MatchRepository.java
Other components
- User
- Mongo GridFS
Connections 22
- User → Application routes: uses
- Application routes → Profile experiences: routes to
Frontend/CricLively/src/App.tsx - Application routes → Match experiences: routes to
Frontend/CricLively/src/App.tsx - Application routes → Tournament dashboard: routes to
Frontend/CricLively/src/App.tsx - Application routes → Scorer interface: routes to
Frontend/CricLively/src/App.tsx - Application routes → Score viewer: routes to
Frontend/CricLively/src/App.tsx - HTTP client → User: requests
Frontend/CricLively/src/API/client.ts - Player endpoints → Profile service: registers via
Backend/CricLively/src/main/java/com/CricLively/RestController/PlayerController.java - Player endpoints → Player service: updates via
Backend/CricLively/src/main/java/com/CricLively/RestController/PlayerController.java - Profile endpoints → Profile service: delegates to
Backend/CricLively/src/main/java/com/CricLively/RestController/ProfileController.java - Profile service → Player repository: accesses players
Backend/CricLively/src/main/java/com/CricLively/Service/ProfileService.java - Profile service → Profile repository: accesses profiles
Backend/CricLively/src/main/java/com/CricLively/Service/ProfileService.java - Player service → Player repository: loads and saves
Backend/CricLively/src/main/java/com/CricLively/Service/PlayerService.java - Player service → Image storage: stores images
Backend/CricLively/src/main/java/com/CricLively/Service/PlayerService.java - Image storage → Mongo GridFS: stores and loads
Backend/CricLively/src/main/java/com/CricLively/Service/ImageStorageService.java - Match service → Team repository: looks up teams
Backend/CricLively/src/main/java/com/CricLively/Service/MatchService.java - Match service → Tournament repository: looks up tournaments
Backend/CricLively/src/main/java/com/CricLively/Service/MatchService.java - Scoring endpoints → Scoring rules: dispatches scoring
Backend/CricLively/src/main/java/com/CricLively/RestController/ScoringController.java - Scoring rules → Ball repository: reads and writes balls
Backend/CricLively/src/main/java/com/CricLively/Service/ScoringService.java - Scoring rules → Match repository: loads and saves matches
Backend/CricLively/src/main/java/com/CricLively/Service/ScoringService.java - Scoring rules → Player repository: loads player names
Backend/CricLively/src/main/java/com/CricLively/Service/ScoringService.java - Profile service → Profile list DTO: maps profiles
Backend/CricLively/src/main/java/com/CricLively/Service/ProfileService.java