Give needs-review entries a structured open question and surface it

Abierto
  • ¿Algo no está bien?
#211 1 comentario 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, node.js
Área
tooling

Línea de trabajo

Start with the V9 - Deprecated: rule in site/checks.mjs and the age-only sorting in site/lib/reverify.mjs (lines 23-31), then see where needs-review is documented in CONTRIBUTING.md. Done means every needs-review entry carries a - Review: line that the checks enforce, the question appears on the entry page and in data.json, and the monthly re-verify issue lists them. The open decision on grandfathering existing entries needs a maintainer answer before implementing. Run npm run check to verify.

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

Descripción

enhancement priority: medium

Summary

43 entries are needs-review, none with a machine-readable statement of what is unresolved. deprecated requires a - Deprecated: line (V9); needs-review has no equivalent. The re-verify batch sorts by age only, so a recently checked needs-review entry waits months and contributors never see its question.

Related: #99

Where

  • CONTRIBUTING.md:16
  • site/lib/reverify.mjs:23-31
  • site/checks.mjs (V9 - Deprecated: rule)

Suggested fix

  • Add a - Review: marker line, enforced the way V9 is.
  • Show it on the entry page and in data.json.
  • Append an "Open questions" section to the monthly re-verify issue.

Open question: grandfather existing entries for one cycle while backfilling?

Acceptance criteria

  • Every needs-review entry states its open question
  • The re-verify issue lists them

Getting started

  • Relevant files: site/checks.mjs, site/lib/reverify.mjs, site/lib/entry-page.mjs
  • How to run tests: npm test (unit tests), npm run check (tests + validate + build). Node 22+, no dependencies.
  • Related docs: site/README.md, CONTRIBUTING.md

Filed by repo-audit/full-audit at 982fcd9. Severity: medium. Effort: M. audit-key: enhancement|site/checks.mjs|needs-review-marker

Lenguaje dominante
JavaScript
Estrellas
58
Forks
15
Merge medio
1 d 14 h
PR fusionados (30 d)
11

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 TMHSDigital/Free-Game-Dev-Assets

Todos los issues de TMHSDigital/Free-Game-Dev-Assets

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.