How ma813/trekking works
This repository implements a browser-based multiplayer card game with a .NET backend. Players enter through the frontend, use account and card-management features, and can participate in real-time lobby/game flows; backend APIs also support statistics and persisted game results. The sampled source supports the frontend composition, backend API-to-repository calls, and core game/lobby relationships, but not all frontend-to-backend HTTP wiring. Major unsampled UI and backend subsystems are represented at their exact tree paths.
Main entry points: apiClient.ts API Controllers · App.tsx App and Pages · Repository.cs Repository Facade · Game.cs Game Rules
Components 23
Frontend
- App and Pages
Frontend/src/App.tsx - Game UI
Frontend/src/components/Game.tsx - Lobby UI
Frontend/src/components/Lobby.tsx - Authentication UI
Frontend/src/components/AuthPage.tsx - Card and Deck UI
Frontend/src/components/AllCardsPage.tsx - Stats UI
Frontend/src/components/StatsPage.tsx - API Controllers
Frontend/src/controllers/apiClient.ts - Hub Client
Frontend/src/services/LobbyHubClient.ts
Backend APIs
- Authentication API
Backend/Controllers/AuthController.cs - Cards API
Backend/Controllers/CardsController.cs - Deck Extensions API
Backend/Controllers/DeckExtensionsController.cs - Statistics API
Backend/Controllers/StatsController.cs
Real-time Game
- Lobby Service
Backend/Services/LobbyService.cs - Lobby Handler
Backend/Handlers/LobbyHandler.cs - Game Rules
Backend/Models/Game.cs - Player State
Backend/Models/Player.cs - Game Data
Backend/DTO/GameDto.cs
Persistence and Media
- Repository Facade
Backend/Repositories/Repository.cs - Application Database
Backend/AppDbContext.cs - Game and Account Records
Backend/Models - Image Storage
Backend/Services/BlobStorageService.cs
Other components
- Player
- Blob or Local Assets
Connections 30
- Player → App and Pages: uses
- App and Pages → Authentication UI: renders
Frontend/src/App.tsx - App and Pages → Lobby UI: renders
Frontend/src/App.tsx - App and Pages → Game UI: renders
- App and Pages → Card and Deck UI: renders
Frontend/src/App.tsx - App and Pages → Stats UI: renders
Frontend/src/App.tsx - Lobby UI → Hub Client: uses
- Game UI → Hub Client: uses
- Authentication UI → API Controllers: uses
- Card and Deck UI → API Controllers: uses
- Stats UI → API Controllers: uses
- API Controllers → Authentication API: HTTP requests
- API Controllers → Cards API: HTTP requests
- API Controllers → Deck Extensions API: HTTP requests
- API Controllers → Statistics API: HTTP requests
- Hub Client → Lobby Service: real-time messages
- Lobby Service → Lobby Handler: uses
Backend/Services/LobbyService.cs - Lobby Handler → Game Rules: manages
Backend/Handlers/LobbyHandler.cs - Game Rules → Player State: updates
Backend/Models/Game.cs - Game Rules → Repository Facade: loads and saves
Backend/Repositories/Repository.cs - Game Rules → Game Data: sends game data
Backend/Models/Game.cs - Authentication API → Repository Facade: reads and writes
Backend/Controllers/AuthController.cs - Authentication API → Image Storage: uploads profile image
Backend/Controllers/AuthController.cs - Cards API → Repository Facade: reads and writes
Backend/Controllers/CardsController.cs - Cards API → Image Storage: uploads card image
Backend/Controllers/CardsController.cs - Deck Extensions API → Repository Facade: reads and writes
Backend/Controllers/DeckExtensionsController.cs - Statistics API → Repository Facade: reads results
Backend/Controllers/StatsController.cs - Repository Facade → Application Database: queries
Backend/Repositories/Repository.cs - Application Database → Game and Account Records: persists
Backend/AppDbContext.cs - Image Storage → Blob or Local Assets: uploads images
Backend/Services/BlobStorageService.cs