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

[READY][SPA][P10] Gameplay MVP-del 4: Reconnect/loading/error states i Angular player flow #187

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

Problem
MVP gameplay-flow i SPA mangler robuste reconnect/loading/error states for player-view. Det giver skrøbelig adfærd ved netværksblip og underminerer testbarheden af én fuld runde uden reload.

Værdi
Højere driftssikkerhed i real-world sessions, færre support-fejl og bedre grundlag for staging smoke på SPA-sporet.

Hvorfor nu
Efter next-round/final leaderboard-sporet (#180/#185) er næste naturlige lille bid at lukke resilience-gap, før cutover-forberedelse intensiveres.

Acceptance

  • Player-flow viser tydelige loading states på join/guess/reveal transitions.
  • Ved simuleret reconnect (tab refresh/netværksafbrud) kan session-state genskabes uden page-loop.
  • Fejltilstande har brugerrettet fallback (retry + tilbage til lobby/join), ikke blank state.
  • Flowet bruger eksisterende Django endpoints uden kontraktændringer.

Afgrænsning

  • Ingen nye game-regler eller scoring-logik.
  • Ingen host-dashboard redesign.
  • Ingen feature-flag/cutover-ændringer her.
Problem MVP gameplay-flow i SPA mangler robuste reconnect/loading/error states for player-view. Det giver skrøbelig adfærd ved netværksblip og underminerer testbarheden af én fuld runde uden reload. Værdi Højere driftssikkerhed i real-world sessions, færre support-fejl og bedre grundlag for staging smoke på SPA-sporet. Hvorfor nu Efter next-round/final leaderboard-sporet (#180/#185) er næste naturlige lille bid at lukke resilience-gap, før cutover-forberedelse intensiveres. Acceptance - Player-flow viser tydelige loading states på join/guess/reveal transitions. - Ved simuleret reconnect (tab refresh/netværksafbrud) kan session-state genskabes uden page-loop. - Fejltilstande har brugerrettet fallback (retry + tilbage til lobby/join), ikke blank state. - Flowet bruger eksisterende Django endpoints uden kontraktændringer. Afgrænsning - Ingen nye game-regler eller scoring-logik. - Ingen host-dashboard redesign. - Ingen feature-flag/cutover-ændringer her.
architecture-bot added the bot-tasknice-to-havearchitectui labels 2026-03-01 16:25:59 +01:00
architecture-bot added frontendneed-to-have and removed nice-to-have labels 2026-03-01 17:27:56 +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 Label architect bot-task frontend 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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#187
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?