Files

Josep Piguillem 233c46e9fa feat: push notifications on each device (Web Push)

- What reaches the bell also reaches the devices where the person
  turned «Avisos en este dispositivo» on, with TaskStream closed: the
  Notifier sends each new notification encrypted (aes128gcm) and signed
  with VAPID, and forgets subscriptions the push service dropped
  (404/410). A failure never blocks the event stream.
- The API keeps one subscription per device (push_subscriptions) and
  exposes the VAPID public key in the notification settings; GraphQL
  subscribePush/unsubscribePush, REST /me/push-subscriptions. Without
  VAPID_PUBLIC_KEY and VAPID_PRIVATE_KEY push is off.
- The web registers /push-sw.js, a service worker that only shows the
  notification and opens its ticket on a tap (no caching, served
  without cache by nginx), and a manifest that makes it installable,
  which iPhones need for push.
- The bell's toggles show their text next to them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-15 08:38:07 +02:00

src

feat: push notifications on each device (Web Push)

2026-10-15 08:38:07 +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-infrastructure

Adaptadores de salida del tracker.

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

Contenido

postgres/: lookups de escritura (project_keys, issue_sequences, release_names), ReleaseIssuesRepository y TrackerStreamsRepository (consultan el event store: tickets y releases de un proyecto, comentarios y enlaces de un ticket).
mongo/: esquemas del read model (incluida la línea temporal issue_timeline), repositorios Find* y UpsertMaterialized* (upsert idempotente por versión) y StatusCategoryBackfill (al arrancar, rellena la categoría del estado en los tickets proyectados antes de existir).
realtime/: RedisChangeFeed (canales de Redis pub/sub por proyecto, ticket y usuario).
identity/: IdentityUserDirectory, capa anticorrupción hacia el contexto de identidad.

Comandos

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

Reglas de dependencia entre capas: Arquitectura.