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

test(server): finish the CONFIG.md gate: schema rows and types, env read in its own gate, table and anchor integrity

Abierto
  • ¿Algo no está bien?
#8,564 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, markdown
Área
testing

Línea de trabajo

Start in packages/server/tests/config-supported-keys-docs.test.js and reuse the CONFIG.md parser already there, then read PR #8563 to see how the features inventories and env locations are gated. Add three checks: each CONFIG_SCHEMA key has a row whose type matches, each documented env override is read inside its own flag's gate function, and table column counts and anchor links are valid. Done means all three run in Server Tests and each fails when the mutations in the issue are applied.

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

Descripción

from-review testing

Follow-up from #7032 / PR #8563. PR #8563 gates the CONFIG.md features inventories, the three env-var locations, and the fail-closed numerals against the real features.<flag> === true gates in src, inside packages/server/tests/config-supported-keys-docs.test.js. Three checks from #7032's original list are still not in the repo:

  • Schema rows. Every CONFIG_SCHEMA key has a CONFIG.md row, and its documented type matches the schema's type.
  • Env override in its own gate. Each documented env override is read in that flag's own gate function, not merely somewhere in src/ (PR #8563 checks only that the literal process.env.<NAME> read exists somewhere).
  • Markdown integrity. Table column counts and anchor links (#7032 reported these as passing at the time).

Acceptance

  • Each check lives in the existing CONFIG.md gate file and reuses its parser. It runs in Server Tests.
  • Each check is proven red by a mutation:
    • a schema key with no row;
    • a row whose type disagrees with the schema;
    • an env override read only outside its gate;
    • a broken table row or anchor.
Lenguaje dominante
JavaScript
Estrellas
7
Forks
1
Merge medio
2 h 57 min
PR fusionados (30 d)
331

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 blamechris/chroxy

Todos los issues de blamechris/chroxy

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.