games: add a shared catalogue and session lifecycle

Aperta
  • Qualcosa non va?
#58 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
next.js, react, typescript
Ambito
frontend, full-stack, testing

Direzione di ricerca

Start by reading the existing Pattern Sprint and Digit Recall implementations under src/app/games/, then inspect the related work in #24. Map their routes and behavior against the proposed src/features/games/ boundary and identify the relevant checks for lifecycle, deterministic generation, and keyboard and mobile use. Done means both games use the shared catalogue and lifecycle, retain their URLs and behavior, and have the contributor guide and coverage described in the issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement games help wanted

Part of #24. Build this before the new game implementations.

Student problem

Every placement game needs clear instructions, predictable controls, timing and useful results. Separate implementations make the experience inconsistent and make new games harder to contribute.

Scope

  • Add a documented src/features/games/ boundary: pure rules and generators separate from React, browser storage, authentication and payments. Keep src/app/games/ routes thin.
  • Define a typed catalogue with stable game ID, skill, original instructions, difficulty options, supported modes and rules version.
  • Share the lifecycle: instructions, running, feedback/results and restart. Define a result contract for history and mixed sessions; scoring remains explicit per game.
  • Support untimed learning and clearly labelled timed practice where appropriate. Start only after an explicit action; use an injected clock/random source and document deadline/background-tab behavior.
  • Move Pattern Sprint and Digit Recall onto these boundaries, preserving their URLs and existing behavior.
  • Keep practice free, available without login or backend configuration, usable by keyboard and touch, and respectful of reduced motion. Do not rely on color alone.
  • Use original code, puzzle content and assets. State that exercises are independent practice rather than official employer assessments.

Done when

  • Tests cover start, completion, timeout, restart, duplicate input and deterministic generation.
  • Browser checks complete both existing games on desktop/mobile and exercise keyboard controls.
  • A contributor guide explains how to register a game, define its rules/scoring and run relevant checks.

Saved history, cloud synchronization, billing and leaderboards are separate work.

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
8h 58m
PR unite (30g)
37

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di procoderji-com/procoderji

Tutte le issue di procoderji-com/procoderji

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.