Files
task-stream/libs/web/tracker/domain
Josep Piguillem ea4ef82239 feat: replies to comments
A comment can answer another one (replyTo), one level deep: answering a
reply joins the same thread, and it must be on the same ticket. Whoever
wrote the comment gets a new REPLIED notification, and the activity says
"respondió a un comentario".

A comment deleted while it has replies stays, without its text
(deleted: true), so the thread still reads; it goes with its last reply
and does not count in commentCount.

The ticket page shows threads with their replies indented and a
"Responder" box; REST, GraphQL and the MCP (add_comment, get_issue) take
and show replyTo. Existing comments are unchanged. Docs, Word and PDF
updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 11:14:37 +02:00
..
2026-10-09 11:14:37 +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
2026-10-03 13:40:26 +02:00

web-tracker-domain

Modelo del tracker en el cliente.

  • Import: @task-stream/web/tracker/domain
  • Capa: domain · Tags: scope:web-tracker, type:domain

Contenido

  • Modelos (Project, IssueSummary, Issue, Release…), enums e inputs.
  • Configuración por proyecto (ProjectSettings, StatusCategory) y Workflow: nombres, colores, iconos, categorías, transiciones permitidas y estados que piden motivo, con un nombre legible para ids que ya no están configurados.
  • Estadísticas (ProjectAnalytics, ReleaseBurnup).
  • Puertos: ProjectsGateway, IssuesGateway, CommentsGateway, ReleasesGateway, ActivityGateway, UsersGateway, TrackerRealtimeGateway.

Comandos

npx nx lint web-tracker-domain
npx nx test web-tracker-domain    # Jest

Reglas de dependencia entre capas: Arquitectura.