Files

Josep Piguillem 199b60e4ce feat: conversations on a ticket are settled, and you see who is typing

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>

2026-10-19 22:35:46 +02:00

src

feat: conversations on a ticket are settled, and you see who is typing

2026-10-19 22:35:46 +02:00

eslint.config.mjs

first commit

2026-10-03 13:40:26 +02:00

project.json

first commit

2026-10-03 13:40:26 +02:00

README.md

feat: per-project workflow settings, statistics and "my work" home

2026-10-06 20:53:45 +02:00

tsconfig.json

first commit

2026-10-03 13:40:26 +02:00

tsconfig.lib.json

first commit

2026-10-03 13:40:26 +02:00

README.md

web-tracker-infrastructure

Adaptadores GraphQL del tracker.

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

Contenido

graphql/*.graphql: operaciones; generated.ts lo genera npx nx run web:codegen.
adapters/: implementaciones de los gateways y mappers.ts (GraphQL → dominio, y la configuración de vuelta a input sin __typename).
provideTrackerInfrastructure().

Comandos

npx nx lint web-tracker-infrastructure

Reglas de dependencia entre capas: Arquitectura.