a package with a `bin` entry: console output is the product, not debug logging (M2)

Abierto
#425 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
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
node.js, typescript
Área
cli, tooling

Línea de trabajo

Start with centralized-logging.ts around lines 21-39 and compare its TypeScript handling with the Python PY_ALLOWED behavior. Trace the package.json bin entry into the command layer and inspect the cited src/cli/*, audit-engine.ts, and hooks/installer.ts output. Keep library logging violations visible; done means CLI log/info/warn output is exempted while debug/trace remains counted and logging sink modules are recognized or configurable.

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

Descripción

bug

Found in the 8.0.0 self-audit triage: RoC 7.29.1 (npm, 5fc54afe) on a clean clone of develop at 2d2fa9a, with typescript resolvable (verdict compliance, 0 failed / 46 warnings). The bucket method and per-law tables are kept by QA; counts are from that run.

What happens

Absolute Zero Tolerance (console template, 15 of 20 false) and Centralized Logging (10 of 18 false) count every console.* call as stray logging. In a CLI, console.log/info/warn in the command layer and report renderer is the user interface: src/cli/*, the report rendering in audit-engine.ts (about 70 of its 84 calls), hooks/installer.ts progress output. The Python branch of Centralized Logging already exempts CLI entry points (PY_ALLOWED); the TypeScript branch does not (centralized-logging.ts:37-39). The logger allowlist accepts only files named logger.service.ts|main.ts (:21-22), so a project's own logging module (logging-utils.ts) is flagged too.

Real debt remains and should stay visible: library code that bypasses the project's logger (e.g. a cache write warning, [DEBUG] output in a discovery helper, a console.log inside a law service during an audit).

Suggested direction

When package.json declares bin, treat console.log/info/warn in the modules reachable from the bin entry's command layer as product output and keep counting console.debug/trace; recognise a logging sink module (logger., logging, log.ts) or make it configurable.

Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
38 min
PR fusionados (30 d)
96

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 Rule-Of-Code/RoC

Todos los issues de Rule-Of-Code/RoC

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.