Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Study plans: curated problem paths

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, json, next.js, node.js
Área
backend, full-stack

Línea de trabajo

Start by reading the existing problem definitions under backend/arena/ and the validation command in package.json or scripts/; inspect the current routes and tests for progress and badges. The requested work spans plan data, validation, player progress, UI, and badges, so first map those entry points. Done means at least three plans, the specified validation and route tests, and both npm test and node scripts/check-boundary.js passing.

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

Descripción

enhancement help wanted

Practice is one big list. Players who want to get better at something specific, like graphs before an interview, have to find and order the problems themselves.

Design

  • Study plans: curated, ordered sets of problems with a short intro per step. For example "Graphs in 7 days", "Dynamic programming from zero", "Interview warm-up week".
  • Defined as files in the repo (backend/arena/plans/<id>.json), so anyone can contribute one through a pull request, like problems.
  • Each step lists one or more problems and an optional note on what the step teaches.
  • Progress is saved per player. The plan page shows done, in progress and next.
  • A plan can unlock a profile badge on completion, using the existing badge system.

Validation

Extend npm run validate:problems (or add validate:plans) to check that every problem a plan references exists, no step is empty, and ids are unique.

Definition of done

  • At least three real plans written from the existing 45 problems, sensibly ordered by difficulty.
  • Route tests for progress tracking, and for a plan whose problem was removed.
  • npm test and node scripts/check-boundary.js pass.
Lenguaje dominante
JavaScript
Estrellas
0
Forks
2
Sin PR fusionados en 30 d

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 sennaicodes/codearena

Todos los issues de sennaicodes/codearena

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.