- Mongo read models are @Schema/@Prop classes (SchemaFactory), still loose: the props declared are the indexed or shaped ones. - CommandBus and QueryBus are used by the application services alone. Duplicating a ticket, bulk updates, CSV imports, proposals and emptying the trash chain several commands, so they are service methods now and their composite commands are gone; every command handler is atomic. No forwardRef is needed. - The due-date and trash timers are entry points: they live in the presenters and call the services. The automations event handler has its own file and calls AutomationsService. - The tracker's user directory asks IdentityService; the composition root hands the identity application module to the tracker infrastructure (withIdentity), with no global module. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
api-tracker-infrastructure
Adaptadores de salida del tracker.
- Import:
@task-stream/api/tracker/infrastructure - Capa:
infrastructure· Tags:scope:api-tracker,type:infrastructure
Contenido
postgres/: lookups de escritura (project_keys,issue_sequences,release_names),ReleaseIssuesRepositoryyTrackerStreamsRepository(consultan el event store: tickets y releases de un proyecto, comentarios y enlaces de un ticket).mongo/: esquemas del read model (incluida la línea temporalissue_timeline), repositoriosFind*yUpsertMaterialized*(upsert idempotente por versión) yStatusCategoryBackfill(al arrancar, rellena la categoría del estado en los tickets proyectados antes de existir).realtime/:RedisChangeFeed(canales de Redis pub/sub por proyecto, ticket y usuario).identity/:IdentityUserDirectory, capa anticorrupción hacia el contexto de identidad.
Comandos
npx nx lint api-tracker-infrastructure
npx nx test api-tracker-infrastructure # Jest
Reglas de dependencia entre capas: Arquitectura.