games: save browser history and show per-game progress

Abierto
  • ¿Algo no está bien?
#69 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
next.js, react, typescript
Área
frontend, testing

Línea de trabajo

Start by reading the existing game implementation under src/features/games/, then inspect issue #58 and the integrated game it provides. Define and validate a separate versioned browser-storage format for completed sessions, with bounded deduplication and safe handling of unsupported or corrupt data and unavailable storage. Add recent-attempt feedback, compatible-result comparisons, and a clear-history control; done means the requested unit and browser tests pass while existing practice history and /api/platform/progress remain unchanged.

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

Descripción

enhancement games help wanted

Part of #24. Depends on #58 and at least one integrated game.

Student problem

Results disappear after leaving a game, so students cannot review practice or see whether they are improving.

Scope

  • Add a separate, versioned and validated browser-storage format under src/features/games/.
  • Record game ID, rules version, mode, difficulty, completion time, duration and clearly defined result counts/status.
  • Bound retained history, deduplicate completed sessions, and handle malformed data or unavailable storage without blocking practice.
  • Show recent attempts and useful per-game feedback. Compare results only across compatible game/rules/mode/difficulty.
  • Explain that history stays on this browser/device and provide a clear-history control.
  • Preserve existing question-practice history and the /api/platform/progress contract; game results do not fit its MCQ schema.
  • Keep guest history available without login. These are personal practice records, not verified rankings or hiring-readiness scores.

Done when

  • Tests cover reload, validation, duplicates, retention, clearing, storage failure and unsupported schema versions.
  • A browser test finishes a game, reloads, finds the saved result and clears it.
  • Unsupported or corrupt data fails safely without affecting existing learning progress.

Account sync, backend persistence and public leaderboards require separate scope.

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.