pigui/task-stream
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
e10c9b84bf4d8ab9f63ae81c80120cf0623b7b36
task-stream/libs/api/tracker/application
History
Josep Piguillem 8fe581ff3e feat: a dashboard for clients, behind a secret link 
Owners and admins turn it on in Configuración → General, pick what it
shows (tickets per status, the sprint under way, release forecasts,
open epics and activity per day) and can renew or drop the link. Whoever
has it sees /share/{token} without an account: only those blocks, no
people nor single tickets but the epics, no links into the app, read
again every minute. A renewed or dropped link says it no longer works.

REST (GET/PUT/DELETE /api/projects/{project}/share and the public
GET /api/shared/dashboards/{token}) and GraphQL (dashboardShare,
shareDashboard, unshareDashboard, sharedDashboard). The token is kept
in dashboard_shares and goes with the project.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 10:39:26 +02:00
..
src
feat: a dashboard for clients, behind a secret link
2026-10-16 10:39:26 +02:00
eslint.config.mjs
first commit
2026-10-03 13:40:26 +02:00
jest.config.cts
first commit
2026-10-03 13:40:26 +02:00
project.json
feat: per-project workflow settings, statistics and "my work" home
2026-10-06 20:53:45 +02:00
README.md
feat: public projects, project deletion and sagas
2026-10-07 07:04:20 +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
tsconfig.spec.json
first commit
2026-10-03 13:40:26 +02:00

README.md

api-tracker-application

Casos de uso del tracker (CQRS).

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

Contenido

  • Services: ProjectsService, IssuesService, CommentsService, ReleasesService, ChangesService (subscriptions), WorkflowsService (workflow de cada proyecto para presentar tickets, con una caché de 2 s).
  • commands/: un fichero por command y otro por handler; cargan con WriteAccess (rehydrator) y guardan con commitAndWait().
  • queries/: un fichero por query y otro por handler; leen de los puertos Find*Repository y comprueban el acceso (ReadAccess: miembros, o cualquiera si el proyecto es público; viewerId null = anónimo); SearchMyIssuesQuery y GetUpcomingReleasesQuery cruzan todos los proyectos del usuario («Mi trabajo»).
  • event-handlers/: proyecciones (@EventsHandler) hacia el read model (incluida la línea temporal de cada ticket), notificaciones en tiempo real y feed de actividad.
  • sagas/: ProjectDeletionSaga (cascada al borrar un proyecto y sus tickets), ReleaseArchivedSaga (los tickets sin terminar salen de una release archivada) y UserDeactivatedSaga (desasigna los tickets abiertos de un usuario que Pireon desactiva). Las ejecuta el EventsBridge; sus comandos son internos e idempotentes. Tests en sagas.spec.ts.
  • analytics/: estadísticas y burnup calculados con funciones puras sobre la línea temporal (con tests).
  • ports/: lookups de escritura, Find*, UpsertMaterialized*, ReleaseIssuesRepository, ChangeFeed, UserDirectory.
  • TrackerApplicationModule.withInfrastructure(...).

Cómo añadir un caso de uso: Desarrollo.

Comandos

npx nx lint api-tracker-application
npx nx test api-tracker-application    # Jest

Reglas de dependencia entre capas: Arquitectura.