games: add a shared catalogue and session lifecycle

Aberta
  • Algo errado?
#58 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
next.js, react, typescript
Domínio
frontend, full-stack, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
1
Forks
1
Merge médio
8h 58min
PRs com merge (30d)
37

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de procoderji-com/procoderji

Todas as issues de procoderji-com/procoderji

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.