games: add a shared catalogue and session lifecycle

Abierto
  • ¿Algo no está bien?
#58 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
next.js, react, typescript
Área
frontend, full-stack, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
8 h 58 min
PR fusionados (30 d)
37

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de procoderji-com/procoderji

Todos los issues de procoderji-com/procoderji

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.