- Postgres: every table has a uuid `id` (gen_random_uuid()); the event store keeps its relay order in `seq`, and the lookup tables their uniqueness in constraints of their own. - MongoDB: `_id` is Mongo's ObjectId; `id` is the domain id (the same uuid as the aggregate's stream in Postgres), unique, and every query goes by it. Production starts from empty databases. - Web: linking tickets and hanging one from a parent are picked from a searchable select (links across projects, parents within the project) instead of typing a key; every checkbox is @pi/ui's pi-checkbox. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
web-tracker-presenters
Pantallas del tracker con @pi/ui.
- Import:
@task-stream/web/tracker/presenters - Capa:
presenters· Tags:scope:web-tracker,type:presenters
Contenido
- Rutas
trackerRoutes: inicio (proyectos + «Mi trabajo»,pages/my-work.ts), tablero kanban (drag & drop), ticket, releases, seguimiento, estadísticas, actividad, miembros y configuración (con visibilidad y borrado), más «Explorar» (pages/explore.page.ts). Solo la portada exige sesión. ui/:IssueCardComponent,AvatarsComponent,GoToComponent(«Ir a… WEB-12»),ProjectCardComponent,SeriesChartComponent(gráficas SVG de líneas y áreas apiladas) ycopy.ts(textos y tonos; estados, tipos y áreas salen delWorkflowdel proyecto).
Comandos
npx nx lint web-tracker-presenters
Reglas de dependencia entre capas: Arquitectura.