Files
task-stream/libs/api/tracker/infrastructure
Josep Piguillem 0b65c1c912 feat: attachments on tickets and comments
Files are uploaded over REST, stored on disk (a volume in Docker) and
recorded on the ticket as events; the bytes are written first, so no
attachment ever points at a missing file. Only images, video, audio, PDF
and plain text are shown inline, everything with nosniff and a sandbox CSP.
The web shows thumbnails, uploads by drag and drop or by pasting a
screenshot, and attaches files to new comments.

Also adds `nx run api:contracts`, which writes schema.gql and
openapi.json without starting the API or any database.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 08:35:33 +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.