Added Gamification System with Badge Bitmask, Live Leaderboards, and Anti-Cheat Mechanisms #113

rixitgithub · 2025-11-08T21:02:44Z

Summary by CodeRabbit

New Features
- Gamification system: badges, score tracking, daily streaks and automatic awards
- Real-time leaderboard with live score and badge updates via WebSockets
- Profile page shows score, badges and current streak
- Animated "Badge Unlocked" notification with confetti
- Team improvements: secure join codes, capacity limits and improved matchmaking
- Leaderboard: sorting by score (vs bot) and ELO rating, live updates

_{✏️ Tip: You can customize this high-level summary in your review settings.}

…sistency, including formatting adjustments and type definitions for JudgmentData. - Enhanced score retrieval logic for better clarity and maintainability.

coderabbitai · 2025-11-08T21:02:55Z

Walkthrough

Adds a gamification system: new models, controllers, routes, WebSocket hub and handler, leaderboard/profile/frontend UI updates, and debate flow integration to award scores/badges. Also updates team code generation, team routes, JWT helper, and frontend build deps.

Changes

Cohort / File(s)	Summary
Gamification Models & User `backend/models/gamification.go`, `backend/models/user.go`	New Badge, UserBadge, ScoreUpdate, RateLimitEntry, GamificationEvent types; extends `User` with `Score`, `Badges`, `CurrentStreak`, `LastActivityDate`.
Gamification Backend API `backend/controllers/gamification_controller.go`, `backend/routes/gamification.go`	Implements `AwardBadge`, `UpdateScore`, `GetGamificationLeaderboard` endpoints, rate-limiting, badge checks, score updates, and route handlers delegating to controllers.
WebSocket Gamification Hub & Handler `backend/websocket/gamification.go`, `backend/websocket/gamification_handler.go`	Adds `GamificationClient` registry, thread-safe broadcast (`BroadcastGamificationEvent`), and JWT-authenticated WebSocket handler `GamificationWebSocketHandler`.
Debate Integration `backend/controllers/debatevsbot_controller.go`, `backend/services/debatevsbot.go`, `backend/services/gemini.go`, `backend/services/pros_cons.go`	Triggers gamification after bot debates (score increment, badge awarding, broadcasts), adds logging and Gemini safety settings, and panic recovery around gamification updates.
Auth & Server Setup `backend/controllers/auth.go`, `backend/utils/auth.go`, `backend/cmd/server/main.go`	Initializes gamification fields on signup/Google login; exposes `GetJWTSecret()`; registers gamification WS endpoint, admin and team route setup hooks, and logs MongoDB/Casbin init.
Leaderboard & Profile `backend/controllers/leaderboard.go`, `backend/controllers/profile_controller.go`	Adds `Rating` to `Debater`, computes real stats (debates today/now/experts online), and extends profile JSON with `id`, `score`, `badges`, `currentStreak`.
Team Management `backend/controllers/team_controller.go`, `backend/routes/...`	Replaces `math/rand` with `crypto/rand` for team codes with fallback, enforces `MaxSize` capacity (default 4), recalculates average Elo, and adds team routes setup.
Frontend Gamification Client `frontend/src/services/gamificationService.ts`, `frontend/src/services/teamDebateService.ts`	Adds gamification API client functions (leaderboard, awardBadge, updateScore) and WS factory; normalizes BASE_URL and updates team interfaces.
Frontend UI Components & Pages `frontend/src/components/BadgeUnlocked.tsx`, `frontend/src/components/JudgementPopup.tsx`, `frontend/src/Pages/Leaderboard.tsx`, `frontend/src/Pages/Profile.tsx`, `frontend/src/Pages/DebateRoom.tsx`, `frontend/src/Pages/TeamDebateRoom.tsx`	Adds BadgeUnlocked with confetti, leaderboard real-time updates and sorting, profile badge/streak UI, improved JSON parsing and state consistency in debate rooms, and team debate WS refinements.
Frontend Tooling `frontend/package.json`	Adds `react-confetti` and bumps `vite` devDependency.

Sequence Diagram(s)

sequenceDiagram
    participant Frontend as Client UI
    participant Backend as API Server
    participant DB as MongoDB
    participant WS as Gamification Hub

    Frontend->>Backend: POST /api/update-score or debate ends
    Backend->>DB: Fetch user, atomically increment score, insert ScoreUpdate
    DB-->>Backend: Updated user score
    Backend->>DB: Check/insert badges (UserBadge), update user.Badges
    DB-->>Backend: Badge records
    Backend->>WS: BroadcastGamificationEvent (score_updated / badge_awarded)
    WS->>Frontend: Push event to connected clients
    Frontend->>Frontend: Update leaderboard/profile UI, show BadgeUnlocked

sequenceDiagram
    participant Client as Leaderboard Page
    participant WSHandler as /ws/gamification
    participant Hub as Client Registry
    participant Backend as API Server

    Client->>WSHandler: WebSocket connect (token)
    WSHandler->>Backend: Validate JWT & lookup user
    WSHandler->>Hub: RegisterGamificationClient
    Backend->>Hub: Trigger BroadcastGamificationEvent
    Hub->>Client: Deliver event (badge_awarded / score_updated)
    Client->>Client: Update UI in real time

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Pay extra attention to:
- backend/controllers/gamification_controller.go — rate-limiting logic, atomic updates, badge deduplication, and error paths.
- backend/websocket/gamification.go — concurrent map/mutex usage and client cleanup on write failures.
- backend/controllers/debatevsbot_controller.go — integration points and panic recovery to ensure debate flow stability.
- Frontend WebSocket handling and leaderboard state updates (frontend/src/Pages/Leaderboard.tsx, BadgeUnlocked lifecycle).

Possibly related PRs

Added Admin & Moderator Dashboard with Role-Based Access, Analytics, and Action Logging #112 — overlaps on Casbin RBAC and admin route registrations (server init changes).
Added a new fun pfp avatar selection #103 — related leaderboard/rating field changes and Debater Rating handling.
glicko2 rating, dynamic profile, oauth issue #99 — touches user model and server initialization similarly (user fields and main setup).

Suggested reviewers

bhavik-mangla

Poem

🐰 I hopped through code with nimble paws,

Badges, scores, and WebSocket applause.
Confetti pops and leaderboards cheer,
Streaks ignite — the prizes near!
Hop on, team — the games appear!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main changes in this pull request, which introduces a comprehensive gamification system with badges, leaderboard features, and rate-limiting mechanisms for anti-cheat protection.
Docstring Coverage	✅ Passed	Docstring coverage is 88.24% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 35

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

frontend/src/components/Matchmaking.tsx (1)
133-142: Restore matchmaking reconnection after socket closes

Once the backend closes the socket (or the network blips), onclose drives isConnected to false, which disables the “Start Matchmaking” CTA. But because the effect only runs on the initial mount (its deps never change) and we keep holding the closed socket in wsRef, no new connection is ever created. Users are stuck in a disconnected state until they hard-refresh—this is a regression introduced by the new guard. Please clear the stale reference and trigger the effect to spin up a fresh socket after closure (e.g., null out wsRef and include isConnected in the dependency list so a close causes a reconnect pass).
@@
-    ws.onclose = (event) => {
+    ws.onclose = (event) => {
       setIsConnected(false);
       setIsInPool(false);
+      if (wsRef.current === ws) {
+        wsRef.current = null;
+      }
@@
-  }, [navigate, user?.id, user?.displayName, isLoading]);
+  }, [navigate, user?.id, user?.displayName, isLoading, isConnected]);
Also applies to: 155-155

🧹 Nitpick comments (15)

frontend/src/components/ChatRoom.tsx (3)
110-129: Consider removing redundant null check.

Lines 123-127 check wsRef.current again after it was already verified on lines 112-113. If the WebSocket is in the OPEN state (line 113), wsRef.current cannot be null.

You can simplify by removing the redundant check:
     const timestamp = Math.floor(Date.now() / 1000);
     setMessages((prev) => [
       ...prev,
       { username, message: messageInput, timestamp },
     ]);
-    if (wsRef.current) {
-      wsRef.current.send(
-        JSON.stringify({ type: 'chatMessage', content: messageInput })
-      );
-    }
+    wsRef.current.send(
+      JSON.stringify({ type: 'chatMessage', content: messageInput })
+    );
     setMessageInput('');
131-141: Consider removing redundant null check.

Lines 136-140 check wsRef.current again after verifying readyState on line 132. The redundant check can be removed for cleaner code.

Apply this diff:
   const sendReaction = (reactionType: string) => {
     if (!wsRef.current || wsRef.current.readyState !== WebSocket.OPEN) {
       console.warn('Cannot send reaction: WebSocket not open');
       return;
     }
-    if (wsRef.current) {
-      wsRef.current.send(
-        JSON.stringify({ type: 'reaction', extra: { reaction: reactionType } })
-      );
-    }
+    wsRef.current.send(
+      JSON.stringify({ type: 'reaction', extra: { reaction: reactionType } })
+    );
   };
151-168: Consider removing redundant null check.

Lines 160-162 check wsRef.current again after already verifying readyState on line 155.

Apply this diff:
     if (
       userVoted ||
       !wsRef.current ||
       wsRef.current.readyState !== WebSocket.OPEN
     ) {
       console.warn('Cannot vote: WebSocket not open or already voted');
       return;
     }
-    if (wsRef.current) {
-      wsRef.current.send(JSON.stringify({ type: 'vote', extra: { option } }));
-    }
+    wsRef.current.send(JSON.stringify({ type: 'vote', extra: { option } }));
     setVoteResults((prev) => ({
       ...prev,
       [option]: (prev[option] || 0) + 1,
     }));
backend/controllers/profile_controller.go (1)
193-201: Normalize badges to an empty array.

For legacy users the badges slice will be nil, so this response serializes badges as JSON null. New UI that expects an array (e.g., badges.map(...)) will crash unless it defensively checks for null. Please default to an empty slice just before building the payload.
+	badges := user.Badges
+	if badges == nil {
+		badges = []string{}
+	}
 	c.JSON(http.StatusOK, gin.H{
 		"profile": gin.H{
 			"id":          user.ID.Hex(),
 			"displayName": displayName,
 			"email":       user.Email,
 			"bio":         user.Bio,
 			"rating":   int(user.Rating),
-			"score":       user.Score,
-			"badges":      user.Badges,
+			"score":       user.Score,
+			"badges":      badges,
 			"currentStreak": user.CurrentStreak,
backend/routes/team.go (1)
10-27: Consider standardizing route parameter names.

The routes use both :id and :teamId for team identifiers. This inconsistency can be confusing.

Consider standardizing to :teamId throughout:
-		teamRoutes.GET("/:id", controllers.GetTeam)
-		teamRoutes.POST("/:id/join", controllers.JoinTeam)
-		teamRoutes.POST("/:id/leave", controllers.LeaveTeam)
+		teamRoutes.GET("/:teamId", controllers.GetTeam)
+		teamRoutes.POST("/:teamId/join", controllers.JoinTeam)
+		teamRoutes.POST("/:teamId/leave", controllers.LeaveTeam)
Update the corresponding controller methods to use c.Param("teamId") instead of c.Param("id").
frontend/src/components/BadgeUnlocked.tsx (2)
13-27: Consider externalizing badge configuration.

The badge icons and descriptions are hardcoded. For better maintainability as the badge system grows, consider moving these to a configuration file or fetching them from the backend.

47-54: Consider conditional resize listener.

The resize listener runs continuously even when the dialog is closed. For a minor optimization, you could conditionally add/remove the listener based on isOpen:
 useEffect(() => {
+  if (!isOpen) return;
+  
   const handleResize = () => {
     setWindowSize({ width: window.innerWidth, height: window.innerHeight });
   };

   window.addEventListener("resize", handleResize);
   return () => window.removeEventListener("resize", handleResize);
-}, []);
+}, [isOpen]);
backend/models/gamification.go (1)

10-55: Consider adding database indexes and note type inconsistency.

Index Recommendations: For frequently queried fields, consider adding indexes in your database setup:

UserBadge.UserID and UserBadge.BadgeName (composite index for lookups)

ScoreUpdate.UserID and ScoreUpdate.CreatedAt (for user score history)

RateLimitEntry.UserID and RateLimitEntry.Action (composite for rate limit checks)

Type Inconsistency: GamificationEvent.UserID (line 49) is a string while other structs use primitive.ObjectID. This is likely intentional for WebSocket serialization, but consider documenting this decision.

frontend/src/components/TeamMatchmaking.tsx (5)

50-65: Complex captain check logic.

The captain verification logic handles multiple ID formats with type assertions. While functional, this suggests inconsistent data structures from the backend. Consider standardizing the API response format to always return strings for IDs to simplify this logic.

71-106: Consider optimizing debate status polling.

The 2-second polling interval (line 103) for all team members could be optimized:

Increase interval: For non-real-time updates, consider 5-10 seconds.

Use WebSocket: Since the PR adds WebSocket support, consider using it for real-time debate notifications instead of polling.

Conditional polling: Only poll when the tab is visible using the Page Visibility API.

109-124: Matchmaking polling could use WebSocket.

Similar to the debate polling, this 3-second interval could be replaced with WebSocket notifications for a more responsive and efficient experience. The backend already has WebSocket infrastructure at /ws/team.

156-175: Hardcoded debate topic limits functionality.

Line 160 uses a hardcoded topic "Should AI be regulated?" with a comment noting it "Could be dynamic". Consider allowing the captain to select or input a topic before creating the debate to improve user experience.

126-142: Replace alert() with toast notifications.

Lines 128, 139, 152, and 173 use browser alert() for error messages. Consider using a toast notification system (like the one likely available in your UI library) for better UX.
backend/websocket/gamification.go (1)
41-47: Consider defensive connection closing.

Line 45 closes the WebSocket connection without checking if it's already closed. While gorilla/websocket typically handles this gracefully, consider adding error handling for robustness:
 func UnregisterGamificationClient(client *GamificationClient) {
 	gamificationMutex.Lock()
 	defer gamificationMutex.Unlock()
 	delete(gamificationClients, client)
-	client.Conn.Close()
+	if err := client.Conn.Close(); err != nil {
+		log.Printf("Error closing gamification client connection: %v", err)
+	}
 	log.Printf("Gamification client unregistered. Total clients: %d", len(gamificationClients))
 }
frontend/tsconfig.app.tsbuildinfo (1)

1-1: Consider excluding build artifacts from version control.

The tsconfig.app.tsbuildinfo file is a TypeScript build artifact that gets regenerated on each build. Consider adding *.tsbuildinfo to .gitignore to avoid unnecessary merge conflicts and repository bloat.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f29be62 and f388bd6.

⛔ Files ignored due to path filters (1)

frontend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (58)

backend/cmd/server/main.go (3 hunks)
backend/controllers/auth.go (2 hunks)
backend/controllers/debatevsbot_controller.go (3 hunks)
backend/controllers/gamification_controller.go (1 hunks)
backend/controllers/leaderboard.go (3 hunks)
backend/controllers/profile_controller.go (1 hunks)
backend/controllers/team_controller.go (1 hunks)
backend/controllers/team_debate_controller.go (1 hunks)
backend/controllers/team_matchmaking.go (1 hunks)
backend/db/db.go (1 hunks)
backend/middlewares/auth.go (2 hunks)
backend/models/gamification.go (1 hunks)
backend/models/team.go (1 hunks)
backend/models/user.go (1 hunks)
backend/routes/gamification.go (1 hunks)
backend/routes/team.go (1 hunks)
backend/services/coach.go (2 hunks)
backend/services/debatevsbot.go (2 hunks)
backend/services/gemini.go (1 hunks)
backend/services/pros_cons.go (2 hunks)
backend/services/team_matchmaking.go (1 hunks)
backend/services/team_turn_service.go (1 hunks)
backend/services/transcriptservice.go (1 hunks)
backend/utils/auth.go (1 hunks)
backend/websocket/gamification.go (1 hunks)
backend/websocket/gamification_handler.go (1 hunks)
backend/websocket/matchmaking.go (2 hunks)
backend/websocket/team_debate_handler.go (1 hunks)
backend/websocket/team_websocket.go (1 hunks)
backend/websocket/websocket.go (3 hunks)
frontend/package.json (3 hunks)
frontend/src/App.tsx (4 hunks)
frontend/src/Pages/About.tsx (5 hunks)
frontend/src/Pages/DebateRoom.tsx (5 hunks)
frontend/src/Pages/Game.tsx (6 hunks)
frontend/src/Pages/Leaderboard.tsx (8 hunks)
frontend/src/Pages/MatchLogs.tsx (5 hunks)
frontend/src/Pages/OnlineDebateRoom.tsx (15 hunks)
frontend/src/Pages/Profile.tsx (4 hunks)
frontend/src/Pages/StartDebate.tsx (2 hunks)
frontend/src/Pages/TeamBuilder.tsx (1 hunks)
frontend/src/Pages/TeamDebateRoom.tsx (1 hunks)
frontend/src/Pages/TournamentHub.tsx (9 hunks)
frontend/src/components/BadgeUnlocked.tsx (1 hunks)
frontend/src/components/ChatRoom.tsx (6 hunks)
frontend/src/components/JudgementPopup.tsx (8 hunks)
frontend/src/components/Layout.tsx (1 hunks)
frontend/src/components/Matchmaking.tsx (6 hunks)
frontend/src/components/MatchmakingPool.tsx (1 hunks)
frontend/src/components/Sidebar.tsx (1 hunks)
frontend/src/components/SpeechTranscripts.tsx (2 hunks)
frontend/src/components/TeamChatSidebar.tsx (1 hunks)
frontend/src/components/TeamMatchmaking.tsx (1 hunks)
frontend/src/hooks/useUser.ts (1 hunks)
frontend/src/services/gamificationService.ts (1 hunks)
frontend/src/services/teamDebateService.ts (1 hunks)
frontend/src/services/teamService.ts (1 hunks)
frontend/tsconfig.app.tsbuildinfo (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (32)

frontend/src/components/BadgeUnlocked.tsx (2)

frontend/src/components/ui/dialog.tsx (4)

Dialog (109-109)

DialogContent (114-114)

DialogTitle (117-117)

DialogDescription (118-118)

frontend/src/components/ui/button.tsx (1)

Button (57-57)

backend/routes/team.go (4)

backend/controllers/team_controller.go (11)

CreateTeam (175-246)

GetTeam (249-270)

JoinTeam (273-355)

LeaveTeam (358-416)

RemoveMember (447-518)

UpdateTeamName (49-103)

UpdateTeamSize (106-172)

GetTeamByCode (30-46)

GetTeamMemberProfile (562-588)

GetUserTeams (419-444)

GetAvailableTeams (591-609)

backend/controllers/team_debate_controller.go (3)

CreateTeamDebate (18-94)

GetTeamDebate (97-114)

GetActiveTeamDebate (117-146)

backend/controllers/team_matchmaking.go (4)

JoinMatchmaking (17-69)

LeaveMatchmaking (72-82)

GetMatchmakingStatus (109-129)

GetMatchmakingPool (85-106)

backend/services/team_matchmaking.go (1)

GetMatchmakingPool (125-133)

backend/websocket/matchmaking.go (1)

backend/services/matchmaking.go (1)

GetMatchmakingService (40-49)

backend/middlewares/auth.go (3)

backend/config/config.go (1)

LoadConfig (53-65)

backend/models/user.go (1)

User (10-35)

backend/db/db.go (1)

MongoDatabase (17-17)

backend/websocket/gamification.go (2)

backend/models/gamification.go (1)

GamificationEvent (47-55)

frontend/src/services/gamificationService.ts (1)

GamificationEvent (3-12)

backend/controllers/team_debate_controller.go (3)

backend/db/db.go (1)

GetCollection (21-23)

backend/models/team.go (2)

Team (11-22)

TeamDebate (61-81)

backend/services/team_matchmaking.go (1)

RemoveFromMatchmaking (115-122)

frontend/src/components/ChatRoom.tsx (2)

backend/websocket/websocket.go (1)

Message (63-86)

backend/structs/websocket.go (1)

Message (10-13)

backend/controllers/leaderboard.go (1)

backend/db/db.go (1)

MongoDatabase (17-17)

backend/routes/gamification.go (1)

backend/controllers/gamification_controller.go (3)

AwardBadge (49-161)

UpdateScore (164-257)

GetGamificationLeaderboard (364-431)

backend/websocket/gamification_handler.go (4)

backend/utils/auth.go (1)

GetJWTSecret (39-41)

backend/models/user.go (1)

User (10-35)

backend/db/db.go (1)

MongoDatabase (17-17)

backend/websocket/gamification.go (3)

GamificationClient (13-17)

RegisterGamificationClient (33-38)

UnregisterGamificationClient (41-47)

backend/controllers/team_matchmaking.go (4)

backend/db/db.go (1)

GetCollection (21-23)

backend/models/team.go (1)

Team (11-22)

frontend/src/services/teamService.ts (1)

Team (4-15)

backend/services/team_matchmaking.go (4)

StartTeamMatchmaking (31-62)

RemoveFromMatchmaking (115-122)

GetMatchmakingPool (125-133)

FindMatchingTeam (65-112)

frontend/src/App.tsx (1)

backend/websocket/team_debate_handler.go (1)

TeamDebateRoom (32-36)

frontend/src/components/Matchmaking.tsx (2)

backend/websocket/matchmaking.go (1)

MatchmakingMessage (49-57)

backend/services/matchmaking.go (1)

MatchmakingPool (17-26)

frontend/src/Pages/TeamDebateRoom.tsx (7)

backend/models/team.go (1)

TeamMember (25-32)

frontend/src/services/teamService.ts (2)

TeamMember (17-24)

getTeamDebate (179-192)

backend/websocket/team_debate_handler.go (1)

TeamDebateRoom (32-36)

frontend/src/state/userAtom.ts (1)

userAtom (4-4)

frontend/src/hooks/useUser.ts (1)

useUser (7-60)

frontend/src/utils/auth.ts (1)

getAuthToken (5-7)

frontend/src/services/teamDebateService.ts (1)

getTeamDebate (55-68)

backend/controllers/team_controller.go (3)

backend/db/db.go (1)

GetCollection (21-23)

backend/models/team.go (2)

Team (11-22)

TeamMember (25-32)

frontend/src/services/teamService.ts (2)

Team (4-15)

TeamMember (17-24)

backend/services/team_matchmaking.go (3)

backend/models/team.go (1)

Team (11-22)

backend/db/db.go (1)

GetCollection (21-23)

backend/controllers/team_matchmaking.go (1)

GetMatchmakingPool (85-106)

frontend/src/components/MatchmakingPool.tsx (2)

backend/services/matchmaking.go (1)

MatchmakingPool (17-26)

frontend/src/services/teamDebateService.ts (1)

getMatchmakingPool (117-130)

frontend/src/services/gamificationService.ts (3)

backend/models/gamification.go (1)

GamificationEvent (47-55)

backend/controllers/gamification_controller.go (2)

AwardBadgeRequest (21-25)

UpdateScoreRequest (28-32)

backend/controllers/profile_controller.go (1)

LeaderboardEntry (99-105)

backend/controllers/debatevsbot_controller.go (5)

backend/db/db.go (1)

MongoDatabase (17-17)

backend/models/user.go (1)

User (10-35)

backend/models/gamification.go (3)

ScoreUpdate (29-36)

UserBadge (20-26)

GamificationEvent (47-55)

backend/websocket/gamification.go (1)

BroadcastGamificationEvent (50-83)

frontend/src/services/gamificationService.ts (1)

GamificationEvent (3-12)

backend/models/team.go (3)

frontend/src/services/teamService.ts (3)

TeamMember (17-24)

Team (4-15)

TeamDebate (26-40)

frontend/src/services/teamDebateService.ts (1)

TeamDebate (8-28)

backend/websocket/team_debate_handler.go (1)

TeamDebateMessage (38-47)

frontend/src/Pages/DebateRoom.tsx (1)

frontend/src/services/vsbot.ts (1)

judgeDebate (105-123)

frontend/src/services/teamDebateService.ts (3)

frontend/src/utils/auth.ts (1)

getAuthToken (5-7)

backend/models/team.go (1)

TeamDebate (61-81)

frontend/src/services/teamService.ts (3)

TeamDebate (26-40)

createTeamDebate (158-176)

getTeamDebate (179-192)

backend/websocket/team_websocket.go (4)

backend/services/team_turn_service.go (5)

TeamTurnManager (132-136)

TokenBucket (22-28)

TokenBucketService (16-19)

NewTeamTurnManager (139-144)

NewTokenBucketService (31-35)

backend/utils/auth.go (1)

ValidateTokenAndFetchEmail (136-149)

backend/db/db.go (1)

MongoDatabase (17-17)

backend/models/team.go (2)

TeamDebate (61-81)

Team (11-22)

backend/cmd/server/main.go (4)

backend/websocket/gamification_handler.go (1)

GamificationWebSocketHandler (21-131)

backend/routes/gamification.go (3)

AwardBadgeRouteHandler (9-11)

UpdateScoreRouteHandler (13-15)

GetGamificationLeaderboardRouteHandler (17-19)

backend/routes/team.go (4)

SetupTeamRoutes (10-27)

SetupTeamDebateRoutes (30-37)

SetupTeamChatRoutes (51-53)

SetupTeamMatchmakingRoutes (40-48)

backend/websocket/team_websocket.go (1)

TeamWebsocketHandler (102-388)

backend/websocket/team_debate_handler.go (2)

backend/models/team.go (2)

TeamDebateMessage (84-95)

TeamDebate (61-81)

backend/db/db.go (1)

GetCollection (21-23)

frontend/src/components/TeamMatchmaking.tsx (3)

backend/models/team.go (1)

Team (11-22)

frontend/src/services/teamService.ts (2)

Team (4-15)

createTeamDebate (158-176)

frontend/src/services/teamDebateService.ts (5)

getActiveTeamDebate (71-84)

getMatchmakingStatus (132-145)

joinMatchmaking (87-100)

leaveMatchmaking (102-115)

createTeamDebate (31-52)

backend/controllers/gamification_controller.go (6)

frontend/src/services/gamificationService.ts (3)

AwardBadgeRequest (14-18)

GamificationEvent (3-12)

UpdateScoreRequest (20-24)

backend/db/db.go (1)

MongoDatabase (17-17)

backend/models/user.go (1)

User (10-35)

backend/models/gamification.go (4)

UserBadge (20-26)

GamificationEvent (47-55)

ScoreUpdate (29-36)

RateLimitEntry (39-44)

backend/websocket/gamification.go (1)

BroadcastGamificationEvent (50-83)

backend/controllers/leaderboard.go (1)

Debater (26-34)

backend/websocket/websocket.go (1)

backend/structs/websocket.go (2)

Room (30-37)

Message (10-13)

frontend/src/Pages/TeamBuilder.tsx (3)

backend/models/team.go (2)

TeamMember (25-32)

Team (11-22)

frontend/src/services/teamService.ts (13)

TeamMember (17-24)

Team (4-15)

getAvailableTeams (142-155)

getUserTeams (126-139)

createTeam (61-77)

joinTeam (96-108)

getTeamMemberProfile (308-321)

removeMember (276-289)

deleteTeam (292-305)

updateTeamName (324-339)

updateTeamSize (358-373)

leaveTeam (111-123)

getTeamByCode (342-355)

frontend/src/state/userAtom.ts (1)

userAtom (4-4)

backend/services/team_turn_service.go (2)

backend/db/db.go (1)

GetCollection (21-23)

backend/models/team.go (1)

Team (11-22)

frontend/src/services/teamService.ts (3)

backend/models/team.go (3)

Team (11-22)

TeamMember (25-32)

TeamDebate (61-81)

frontend/src/services/teamDebateService.ts (3)

TeamDebate (8-28)

createTeamDebate (31-52)

getTeamDebate (55-68)

frontend/src/utils/auth.ts (1)

getAuthToken (5-7)

frontend/src/Pages/Leaderboard.tsx (4)

backend/controllers/leaderboard.go (3)

Debater (26-34)

Stat (37-41)

LeaderboardData (20-23)

frontend/src/hooks/useUser.ts (1)

useUser (7-60)

frontend/src/services/gamificationService.ts (3)

fetchGamificationLeaderboard (41-55)

createGamificationWebSocket (93-126)

GamificationEvent (3-12)

frontend/src/services/leaderboardService.ts (1)

fetchLeaderboardData (3-17)

🪛 Biome (2.1.2)

frontend/src/Pages/TeamDebateRoom.tsx

[error] 494-495: Other switch clauses can erroneously access this declaration.
Wrap the declaration in a block to restrict its access to the switch clause.

The declaration is defined in this switch clause:

Safe fix: Wrap the declaration in a block.