Files
task-stream/libs/web/tracker/application
Josep Piguillem f2001aca88 feat: formatted text, a list view, ticket details, public proposals and votes
Formatted text
- Descriptions, comments, replies and release notes render Markdown,
  sanitised with DOMPurify (tested against scripts, handlers and
  javascript: links). A pasted image is uploaded and written as
  ![name](attachment:<id>); the web fetches it with the reader's session,
  so it works on private projects. Every text box has a preview. The
  attachment upload now answers its attachmentId.

List view
- /p/:key/list: every ticket as rows, sortable by any column, filtered by
  text, open/closed, type, priority and assignee; status, priority and
  assignee change in place; bulk edit (the backlog's bar, now shared).

Ticket details
- Reactions on comments (GitHub's eight), for members and viewers.
- Duplicate a ticket: what it says, not where it stands.
- blockedBy: open tickets it waits for (BLOCKS / DEPENDS_ON), worked out
  when reading with one query per board or page; shown on cards, list
  rows and the ticket.

Public proposals
- A public project can take bug reports and ideas from anyone
  (acceptsProposals): POST /api/explore/projects/{project}/proposals and
  the form at /p/:key/proponer. They become tickets labelled «propuesta»,
  opened by TaskStream; a honeypot field and 5 per address every 15
  minutes keep spam out. No e-mail is asked: it would be public.

Votes
- Anyone signed in votes on a public project's tickets, members on a
  private one (voteIssue, PUT/DELETE /api/issues/{issue}/vote): votes and
  voted on each ticket, buttons on the ticket and the roadmap, a column
  in the list. The showcase carries votes and the open proposals.

MCP: vote_issue, duplicate_issue, react_to_comment; listings show
blockers and votes. Docs, Word and PDF updated; chat notifications
(Discord, Slack, Telegram) noted for later.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 21:36:11 +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-application

Estado del tracker (NgRx Signals con eventos) detrás de facades.

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

Contenido

  • Facades (lo que se exporta): ProjectsFacade y HomeFacade («Mi trabajo») (raíz) y ProjectFacade, BoardFacade, IssueFacade (de ruta, con provideProjectFacade(), provideBoardFacade(), provideIssueFacade()). Tests en facades/facades.spec.ts.
  • ExploreFacade (raíz): proyectos públicos, también sin sesión.
  • ProjectFacade también da la visibilidad (setPublic) y el borrado (deleteProject, vuelve a la portada; y si otro lo borra, también), y la configuración del proyecto (workflow, saveSettings) y sus estadísticas (loadAnalytics, loadBurnup).
  • Interno: stores ProjectsStore, ProjectStore, HomeStore, BoardStore, IssueStore y eventos por origen (*PageEvents, *ApiEvents, *RealtimeEvents).
  • board.reducers.ts: transformaciones puras del tablero (movimiento optimista, cambios en vivo por versión).
  • Puerto Notifications.

Patrón de eventos: Cliente web.

Comandos

npx nx lint web-tracker-application
npx nx test web-tracker-application    # Vitest

Reglas de dependencia entre capas: Arquitectura.