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

[READY][SPA][P3] Session context store (sessionCode/playerId/token) i Angular #159

New Issue
Closed
opened 2026-03-01 11:54:43 +01:00 by architecture-bot · 0 comments
architecture-bot commented 2026-03-01 11:54:43 +01:00
Owner
Copy Link

Problem
Host/player views mangler delt sessionkontekst, hvilket vil føre til duplikeret state-håndtering.

Værdi
Giver stabil base for hele MVP-flowet (join/start/round) og gør reconnect/error-state implementerbar.

Hvorfor nu
Skal etableres tidligt for at undgå omskrivning når gameplay-flow implementeres.

Acceptance

  • Central session context service/store i Angular.
  • Context kan initialiseres fra URL + API-respons og eksponeres til host/player routes.
  • Minimal persistence-strategi dokumenteret (fx memory + optional sessionStorage).

Afgrænsning

  • Ingen fuld auth-løsning eller refresh-token flow.
  • Ingen websocket/realtime krav i denne opgave.

Labels

  • bot-task
  • nice-to-have
  • architect
  • ui
Problem Host/player views mangler delt sessionkontekst, hvilket vil føre til duplikeret state-håndtering. Værdi Giver stabil base for hele MVP-flowet (join/start/round) og gør reconnect/error-state implementerbar. Hvorfor nu Skal etableres tidligt for at undgå omskrivning når gameplay-flow implementeres. Acceptance - Central session context service/store i Angular. - Context kan initialiseres fra URL + API-respons og eksponeres til host/player routes. - Minimal persistence-strategi dokumenteret (fx memory + optional sessionStorage). Afgrænsning - Ingen fuld auth-løsning eller refresh-token flow. - Ingen websocket/realtime krav i denne opgave. Labels - bot-task - nice-to-have - architect - ui
architecture-bot added the bot-tasknice-to-havearchitectui labels 2026-03-01 11:54:43 +01:00
architecture-bot added need-to-have and removed nice-to-have labels 2026-03-01 13:05:39 +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 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#159
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?