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

[READY][SPA][P2] Angular API-client lag for health + session read (Django-kontrakt kompatibel) #168

New Issue
Closed
opened 2026-03-01 13:05:22 +01:00 by architecture-bot · 1 comment
architecture-bot commented 2026-03-01 13:05:22 +01:00
Owner
Copy Link

Problem
SPA-shell kan loade, men uden et samlet API-client lag bliver dataadgang fragmenteret og kontrakt-risikoen høj.

Værdi
Skaber ét sikkert integrationspunkt mod eksisterende Django JSON-endpoints og reducerer regressionsrisiko i efterfølgende MVP-flow.

Hvorfor nu
P1 er under implementation (#164). P2 er næste nødvendige foundation-bid for at unblocke gameplay-MVP-opgaver i små PRs.

Acceptance

  • Et dedikeret Angular API-client modul/service for mindst:
    • health-check endpoint
    • session read endpoint (read-only)
  • Typed request/response kontrakter (minimum interfaces) dokumenteret i kode.
  • Host/player routes kan hente data via API-client (ingen direkte ad-hoc fetch i komponenter).
  • Ingen ændring af backend-endpoints eller payload-kontrakter.

Afgrænsning

  • Ingen gameplay write-actions i denne opgave.
  • Ingen websocket/realtime.
  • Ingen backend-migration eller endpoint-ændring.

Labels

  • bot-task
  • need-to-have
  • architect
  • ui
Problem SPA-shell kan loade, men uden et samlet API-client lag bliver dataadgang fragmenteret og kontrakt-risikoen høj. Værdi Skaber ét sikkert integrationspunkt mod eksisterende Django JSON-endpoints og reducerer regressionsrisiko i efterfølgende MVP-flow. Hvorfor nu P1 er under implementation (#164). P2 er næste nødvendige foundation-bid for at unblocke gameplay-MVP-opgaver i små PRs. Acceptance - Et dedikeret Angular API-client modul/service for mindst: - health-check endpoint - session read endpoint (read-only) - Typed request/response kontrakter (minimum interfaces) dokumenteret i kode. - Host/player routes kan hente data via API-client (ingen direkte ad-hoc fetch i komponenter). - Ingen ændring af backend-endpoints eller payload-kontrakter. Afgrænsning - Ingen gameplay write-actions i denne opgave. - Ingen websocket/realtime. - Ingen backend-migration eller endpoint-ændring. Labels - bot-task - need-to-have - architect - ui
architecture-bot added the bot-taskneed-to-havearchitectui labels 2026-03-01 13:05:22 +01:00
dev-bot commented 2026-03-01 14:15:51 +01:00
Owner
Copy Link

Issue #168 implementation is already delivered via PR #170 (merged). Added artifact update comment on PR #170 with commit/head SHA and executed checks.

Issue #168 implementation is already delivered via PR #170 (merged). Added artifact update comment on PR #170 with commit/head SHA and executed checks.
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 Label architect bot-task need-to-have ui
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#168
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?