- Mongo read models are @Schema/@Prop classes (SchemaFactory), still loose: the props declared are the indexed or shaped ones. - CommandBus and QueryBus are used by the application services alone. Duplicating a ticket, bulk updates, CSV imports, proposals and emptying the trash chain several commands, so they are service methods now and their composite commands are gone; every command handler is atomic. No forwardRef is needed. - The due-date and trash timers are entry points: they live in the presenters and call the services. The automations event handler has its own file and calls AutomationsService. - The tracker's user directory asks IdentityService; the composition root hands the identity application module to the tracker infrastructure (withIdentity), with no global module. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
api-tracker-presenters
API GraphQL y REST (OpenAPI) del tracker.
- Import:
@task-stream/api/tracker/presenters - Capa:
presenters· Tags:scope:api-tracker,type:presenters
Contenido
- Resolvers
ProjectResolver,IssueResolver,CommentResolver,ReleaseResolverySubscriptionResolver; solo llaman a services. - Tipos, inputs (con
class-validator) y enums de GraphQL (code-first). http/: controladores RESTProjectsController,IssuesController,CommentsController,ReleasesController(mismos services), DTOs con@nestjs/swaggeryRefs(proyectos y tickets por id o clave; añade a cada ticket sus transiciones permitidas según el workflow de su proyecto).ExploreController(GET /api/explore/projects, sin token). Las lecturas usan@OptionalAuth()yviewerOf(me)(null = anónimo) para servir proyectos públicos sin sesión.common/settings.ts: configuración del proyecto con las transiciones como lista (lo que viaja por GraphQL y REST).
Operaciones disponibles: GraphQL y REST.
Comandos
npx nx lint api-tracker-presenters
npx nx test api-tracker-presenters # Jest
Reglas de dependencia entre capas: Arquitectura.