Files
task-stream/libs/api/tracker/infrastructure
Josep Piguillem 50d3ffd1dd feat: sprints with burndown and carry-over
Plan sprints with dates and a goal, run one at a time per project, and
put tickets in them from the ticket page. The Sprints tab follows the one
under way with its progress and a burndown in tickets or points against
the ideal line. Closing a sprint sends what was left to the next one or
back to the backlog; the board can be filtered by sprint.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 14:59:01 +02:00
..
2026-10-03 13:40:26 +02:00
2026-10-03 13:40:26 +02:00
2026-10-03 13:40:26 +02:00
2026-10-03 13:40:26 +02:00
2026-10-03 13:40:26 +02:00

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), ReleaseIssuesRepository y TrackerStreamsRepository (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 temporal issue_timeline), repositorios Find* y UpsertMaterialized* (upsert idempotente por versión) y StatusCategoryBackfill (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.