games: add a shared catalogue and session lifecycle

Offen
  • Stimmt etwas nicht?
#58 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
next.js, react, typescript
Bereich
frontend, full-stack, testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
1
Ø Merge
8 Std. 58 Min.
Gemergte PRs (30 T.)
37

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus procoderji-com/procoderji

Alle Issues in procoderji-com/procoderji

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.