chore(cli): commands import infrastructure directly, contradicting the documented architecture

Abierto
#470 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
typescript
Área
cli, developer-experience

Línea de trabajo

Start with PR #795, which contains the replacement architecture documentation and the related context-graph, restricted-import, and orchestrator dependency guards. Verify that the documented model matches the presentation-to-runtime composition path, that bounded contexts do not import either outer boundary, and that the architecture gates remain green before closing this issue after the PR merges.

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

Descripción

Context

The old CLI documentation described a strict three-layer model and made command imports from infrastructure/deps appear contradictory.

PR #795 replaces that model with bounded contexts plus two outer boundaries:

  • presentation parses and renders the CLI;
  • runtime is the composition root that wires concrete ports and use cases;
  • kernel and bounded contexts never reach back into either outer boundary.

Decision

A presentation command may call the runtime wiring factory. This is intentional composition, not an application/domain dependency leak.

The factory is invoked per action because project root, output and verbosity are command-specific. Building one global dependency graph in cli.ts would either create it with incomplete command context or move command concerns into the entry point.

The relevant architectural rule is therefore: contexts depend only on permitted inward context edges; presentation and runtime may depend on them. #795 enforces this through the context graph, restricted-import and orchestrator dependency guards.

Acceptance criteria

  • #795 documentation states bounded contexts, not the obsolete three-layer rule.
  • Presentation-to-runtime wiring remains the only outer composition path.
  • No bounded context imports presentation or runtime.
  • #795 architecture gates remain green.
  • #795 links this issue; close it after merge.

Boundary

Do not move the wiring into every command, and do not introduce a global pre-built dependency graph merely to satisfy the former layer diagram.

Lenguaje dominante
TypeScript
Estrellas
481
Forks
45
Merge medio
14 h 36 min
PR fusionados (30 d)
110

Guía de contribución

Abrir la guía de contribución

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 ai-driven-dev/framework

Todos los issues de ai-driven-dev/framework

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.