Josep Piguillem
199b60e4ce
A top-level comment and its replies can be resolved by whoever can
change the ticket (CommentThreadResolvedEvent), with an optional
conclusion added as a reply marked as a decision, so it shows above the
ticket. A settled conversation folds to one line (topic, who settled it
and the conclusion) and can be unfolded or reopened; the header counts
the open ones, and finishing the ticket with one open asks first.
«Ana está escribiendo…» shows in the conversation being answered, at
once: a `typing` mutation publishes to a Redis channel per ticket
(`typing` subscription), never stored. In replies, Enter sends and
Shift+Enter breaks the line, except inside lists and code.
API: resolveThread / PUT-DELETE /api/comments/{id}/resolution, Comment
.resolved/resolvedBy/resolvedAt, typing mutation and subscription. MCP:
resolve_thread.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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) yWorkflow: 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.