laws with no subject in a CLI or library are selected for every TypeScript project (missing requires)

Abierto
#428 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
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
tooling

Línea de trabajo

Start by reading owning-law.ts around owningLawSatisfied and concernIsWaived, then inspect the named law files: cdn-caching-strategy.ts, performance-laws.ts, deployment-laws.ts, and security-laws.ts. Trace how requires and stack checks select laws, and review the related tests for those gates. Done means laws and individual clauses produce no findings when their required project capabilities are absent, including the owning-law case.

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

These laws declare no requires (some not even a stack) and judge any TypeScript repository as if it served a web app or ran a service. On RoC (a CLI/npm package, no deploy target, no server, no web surface, no user data) they produce findings that cannot be fixed honestly:

law finding note
CDN and Caching Strategy 5 hasJsTsSources = "serves web assets" (cdn-caching-strategy.ts:35); own detectionLimit "N/A for a pure backend" is false
Performance Monitoring Standards 3 any non-browser project = backend service needing APM (performance-laws.ts:220)
Incident Response Protocol 3 own detectionLimit admits "no gating"
Launch Readiness Checklist 1 no deploy target (deployment-laws.ts:85-118)
Environment Parity Standards 3 project-level no environments; .env.example reported twice
API Security (authentication) 1 no auth subject (security-laws.ts:307-341)
Authentication Security — passes today only because of its own patterns (see M3)
NX Commands Only Policy 1 no nx.json / nx dependency, gated only by stack typescript
Security Vulnerability Response (privacy clause) 1 no user data
Pre-Deployment Checklist (production logging clause) 1 no production

Suggested direction

Shared, exported requirements such as "runs a service" (REQUIRES_NODE_HTTP_SERVER exists in next-server-laws.ts:33 but is not exported, REQUIRES_SERVERLESS_DEPLOY, firebase/wrangler configs, Dockerfile/Procfile), "web surface" (html/css/web framework deps) and "deploy target", applied to the laws above, plus clause-level gating where one law mixes service and repository concerns. Also: owningLawSatisfied (owning-law.ts:53-79) runs the owning law even when its stack/requires is unmet — unmet should count as satisfied, as concernIsWaived already does.

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.