mirror of
https://github.com/tiennm99/vngeoguessr.git
synced 2026-10-11 03:13:56 +00:00
tiennm99
c2c1ced387
Scoring, the Upstash key adapter, sessions and the leaderboards had no coverage, and they carry the anti-cheat model: server-held coordinates, session TTLs, rank arithmetic. One suite runs against two backing stores. By default @upstash/redis is mocked with an in-memory fake, so `npm test` needs no service and finishes well under a second. With TEST_REDIS=real the mock steps aside and the same files run against a real Redis behind SRH, the proxy Upstash recommends for local work, since the SDK speaks HTTP REST rather than RESP and a plain Redis container cannot serve it alone. Running both is what keeps the fake honest: a semantic it gets wrong shows up as a green unit run and a red integration run. Two tests skip against real Redis, one asserting a response shape only an older SDK produces and one fast-forwarding half an hour to watch a session expire. The suite was checked by mutation rather than by passing alone. Breaking a score band, the key prefix and the session TTL each failed a test; reversing the global trim window did not, because only the city leaderboard was asserted, so that test now covers both scopes. The compose stack doubles as a local Redis for `npm run dev`, which had no credentials to reach one before. package.json also loses the eight unused runtime dependencies removed in the cleanup that follows; they cannot be split from the same file.
2.0 KiB
2.0 KiB
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Documentation
For detailed information about this project, refer to the documentation files in /docs/:
- Project Overview - Project summary, key characteristics, and game mechanics
- Features - Detailed game features, scoring system, and security measures
- Tech Stack - Complete technology stack and dependencies
- Development Guidelines - Development commands, coding standards, and best practices
- Game Flow - Complete gameplay flow from start to finish
- Project Structure - Directory organization and file purposes
Quick Reference
Development Commands:
npm run dev- Start development server with Turbopacknpm run build- Build the application for productionnpm start- Start production servernpm run lint- Run ESLintnpm test- Run tests against the in-memory Redis fake (no service needed)npm run test:integration- Same tests against local Redis (npm run redis:upfirst)
Key Guidelines:
- JavaScript Only: No TypeScript files (.ts, .tsx)
- Function Parameters: Use individual parameters, not object destructuring
- File Modifications: Only modify source code,
/docs, and/plans - Security: Never expose secrets or keys
- Testing: Run
npm testforsrc/lib/changes; inform user when complete - they handle manual testing of the UI
Critical Instructions
When working on this codebase, always:
- Read the relevant documentation files in
/docs/for context - Follow the JavaScript-only approach with individual function parameters
- Maintain server-side security for game sessions and coordinates
- Use existing patterns and libraries already present in the codebase
- Highlight any configuration file changes for manual processing