pigui/task-stream
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
develop
task-stream/libs/web/tracker/application/README.md
Josep Piguillem e656222b54 feat: public projects, project deletion and sagas 
Public projects:
- Project.isPublic (create/update, owners and admins). Anyone can read a
  public project without a token: project, board, tickets, comments,
  history, releases, activity, tracking and statistics, over GraphQL and
  REST. Writes stay for members (401 anonymous, 403 outsiders).
- @OptionalAuth() / @ApiOptionalPireonAuth(): anonymous callers allowed,
  invalid tokens still rejected. ReadAccess lets anonymous viewers read
  public projects only; linked tickets are filtered by visibility.
- publicProjects (GraphQL) and GET /api/explore/projects (REST).
- Web: «Explorar» page, project pages open without a session (read-only
  notice, sign-in hints), public badge, visibility switch in settings,
  no realtime subscriptions without a session.

Project deletion:
- Owner only, confirming the key (deleteProject / DELETE
  /api/projects/{project}?confirm=KEY). The key is freed; the read model
  drops the project and members are notified (web goes home).

Sagas (run by the EventsBridge after projections, durable and ordered):
- ProjectDeletionSaga: project deleted → delete its tickets and releases;
  ticket deleted → purge its comments and drop links from other tickets.
- ReleaseArchivedSaga: unfinished tickets leave an archived release.
- UserDeactivatedSaga: the Pireon webhook records UserDeactivatedEvent in
  the event store (EventRecorder); the tracker unassigns that user's open
  tickets as the system actor.
- Internal idempotent commands; domain refusals are logged and skipped,
  concurrency conflicts retried. Affected streams come from the event store
  (TrackerStreamsRepository).

Tests: domain lifecycle specs, saga specs run like the bridge, facade
tests, e2e for public access, cascade deletion, archived releases and
deactivation webhook. Docs, READMEs, schema.gql/openapi.json and Word/PDF
updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-07 07:04:20 +02:00

1.4 KiB
Raw Permalink Blame History

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.