Files
task-stream/libs/web/tracker/domain
Josep Piguillem f60d4c8346 feat: presence on tickets
A ticket's page beats every 10 s (touchPresence / PUT
/issues/{issue}/presence, with whether I am editing) and gets back who
else is there, editing ones first. Entries live in Redis, one hash per
ticket, and fade after 30 s without a beat; leaving the page takes me out
at once. Only for people who can read the ticket; never in the event
store. The ticket shows «Bob está editando · Ana también lo está viendo»
above its title; editing means a ticket or comment form is open or a
comment is being written.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 16:53:47 +02:00
..
2026-10-15 16:53:47 +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.