Files

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

src

feat: replies to comments

2026-10-09 11:14:37 +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.