wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

[READY][SPA][P9] Angular API-contract guard: typed client + response mappers for host/player flow #186

New Issue
Closed
opened 2026-03-01 16:25:59 +01:00 by architecture-bot · 0 comments
architecture-bot commented 2026-03-01 16:25:59 +01:00
Owner
Copy Link
Copy Source

Problem
Angular SPA-sporet mangler et lille, dedikeret contract-guard lag mod eksisterende Django JSON responses. Uden det stiger regressionsrisikoen i host/player flow, når vi flytter flere gameplay-skærme over.

Værdi
Reducerer integrationsfejl tidligt og gør de næste gameplay-PRs mindre og mere sikre. Beskytter backend-kontrakter under Angular-first migrationen.

Hvorfor nu
Gameplay MVP PRs (#185) er aktive nu; contract-guard bør komme før flere stateful UI-trin, så fejl fanges tæt på API-klienten.

Acceptance

  • Angular API-client har typed request/response interfaces for session/lobby/round endpoints brugt i host+player flow.
  • Mapper/normalizer-lag håndterer mindst 2 kendte nullable/optional felter uden runtime crash.
  • Én lille testpakke (unit/integration light) dokumenterer mapping for success + malformed payload.
  • Ingen backend endpoint- eller payload-ændringer.

Afgrænsning

  • Ingen nye backend-features eller kontraktbrud.
  • Ingen UX-redesign; kun API-klient/mapper + tests.
  • Ingen cutover-flag-ændringer i denne opgave.
Problem Angular SPA-sporet mangler et lille, dedikeret contract-guard lag mod eksisterende Django JSON responses. Uden det stiger regressionsrisikoen i host/player flow, når vi flytter flere gameplay-skærme over. Værdi Reducerer integrationsfejl tidligt og gør de næste gameplay-PRs mindre og mere sikre. Beskytter backend-kontrakter under Angular-first migrationen. Hvorfor nu Gameplay MVP PRs (#185) er aktive nu; contract-guard bør komme før flere stateful UI-trin, så fejl fanges tæt på API-klienten. Acceptance - Angular API-client har typed request/response interfaces for session/lobby/round endpoints brugt i host+player flow. - Mapper/normalizer-lag håndterer mindst 2 kendte nullable/optional felter uden runtime crash. - Én lille testpakke (unit/integration light) dokumenterer mapping for success + malformed payload. - Ingen backend endpoint- eller payload-ændringer. Afgrænsning - Ingen nye backend-features eller kontraktbrud. - Ingen UX-redesign; kun API-klient/mapper + tests. - Ingen cutover-flag-ændringer i denne opgave.
architecture-bot added the bot-taskneed-to-havearchitectui labels 2026-03-01 16:25:59 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No labels architect bot-task need-to-have ui
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#186