How harshitjainhj01/cricmaster works
CRICMASTER is a cricket web application spanning account onboarding, cricket and IPL data, match/player/team views, and supporting features such as news, search, standings, statistics, reviews, and administration. The clearest end-to-end workflow is Firebase sign-in in the browser, token submission to the FastAPI auth route, and session/account persistence. The graph preserves documented-by-source-tree feature branches, but several frontend and route implementations were not sampled; their detailed calls are therefore not inferred.
Main entry points: main.py FastAPI application · auth.js Sign-in UI · auth.py Session and auth API · connection.py Database connection
Components 18
Web client
- Sign-in UI
frontend/js/auth.js - Firebase client setup
frontend/js/firebase-config.js - Cricket feature views
frontend/js/matches.js
API features
- IPL archive API
backend/app/routes/ipl.py - Insights and extras API
backend/app/routes/extra.py - Session and auth API
backend/app/routes/auth.py - Cricket data API
backend/app/routes/cricket.py - Matches API
backend/app/routes/matches.py - FastAPI application
backend/app/main.py
Cricket domain
- Matches and deliveries
backend/app/models/match.py - Ball-by-ball records
backend/app/models/delivery.py - Accounts and profiles
backend/app/models/user.py
Persistence and integrations
- Database connection
backend/app/database/connection.py - Application database
- Firebase token verification
backend/app/services/firebase_auth.py
Other components
- Cricket fan
- Cricket data provider
- RSS news feed
Connections 18
- Cricket fan → Sign-in UI: signs in
frontend/js/auth.js - Sign-in UI → Firebase client setup: initializes
frontend/js/auth.js - Sign-in UI → Firebase token verification: gets ID token
frontend/js/auth.js - Sign-in UI → Session and auth API: posts session
frontend/js/auth.js - Session and auth API → Firebase token verification: verifies token
backend/app/routes/auth.py - Session and auth API → Database connection: opens session
backend/app/routes/auth.py - Database connection → Application database: connects
backend/app/database/connection.py - FastAPI application → Session and auth API: registers route
backend/app/main.py - FastAPI application → Cricket data API: registers route
backend/app/main.py - FastAPI application → Matches API: registers route
backend/app/main.py - FastAPI application → IPL archive API: registers route
backend/app/main.py - FastAPI application → Insights and extras API: registers route
backend/app/main.py - IPL archive API → Database connection: queries database
backend/app/routes/ipl.py - Insights and extras API → Database connection: queries database
backend/app/routes/extra.py - Insights and extras API → RSS news feed: fetches RSS
backend/app/routes/extra.py - Cricket data API → Cricket data provider: requests data
- Matches API → Cricket data provider: requests data
- Cricket feature views → IPL archive API: loads IPL data