TorcidaRequestDto
@raizfc/contracts / TorcidaRequestDto
Type Alias: TorcidaRequestDto
TorcidaRequestDto =
Readonly<{createdAt:ISODateString;decidedAt?:ISODateString;decisionReason?:string;id:ID;name:string;requestedBy:Readonly<{displayName:string;id:ID; }>;slug:Slug;status:TorcidaRequestStatus;territory:TerritorySummaryDto; }>
Defined in: team/team-torcida.dto.ts:19
Team-side view of a torcida's existence request (SPEC-API-TEAM-TORCIDA-001:
GET/POST /teams/:teamId/torcida-requests). Deliberately scoped to exactly what a team needs to
decide — not the full TorcidaManagementDto (identity, members, wallet, join mode, sponsors,
torcida/torcida.dto.ts) that SPEC-DOMAIN-TORCIDA-001 defines. Since IS-MVP-08.1, this is a
projection of the real TorcidaManagementDto (same id, computed by
TorcidaApplicationService/mocks, not a separately stored record) — TeamManagementModule
imports TorcidasModule (mirrors how it already imports ChampionshipsModule for
GET /management/my-entities) to read/decide on torcidas linked to a given team, the same
direction as every other cross-module read in this codebase (never the reverse, which would
cycle). suspended/ended torcidas are surfaced here as 'approved' (they were approved once;
this view has no slot for those two states — TorcidaManagementDto.status is authoritative).