MatchResultDto
@raizfc/contracts / MatchResultDto
Type Alias: MatchResultDto
MatchResultDto =
Readonly<{autoValidated?:boolean;awayScore:number;homeScore:number;matchId:ID;notes?:string;reportedAt:ISODateString;reportedByTeamId:ID;validatedAt?:ISODateString;validatedByTeamId?:ID; }>
Defined in: match/match-result.dto.ts:13
SPEC-DOMAIN-MATCH-001 "Informação de resultado"/"Validação e auto-validação". Persists who
reported the score (reportedByTeamId — needed so validate can require the other side's
authority, the "contraparte" case EP-MVP-06.1/06.2 explicitly left unresolved) and, once
validated, who confirmed it. Deliberately embedded as MatchDto.result (management-only, like
every other field on that DTO) instead of a standalone GET endpoint — SPEC-API-MATCH-001
only lists POST .../result and POST .../validate, no dedicated read route, and the public
projection already exposes homeScore/awayScore/validation (PublicMatchResponse,
IS-MVP-01.3) without needing a second, wider DTO to leak reporter/validator ids publicly.