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

MVP UI need-to-have: guard submit-knapper på manglende spillerkontekst #55

New Issue
Closed
opened 2026-02-28 01:03:24 +01:00 by email-manager · 0 comments
email-manager commented 2026-02-28 01:03:24 +01:00
Owner
Copy Link

Scope-kilde: #16 (epic board) + #17 (MVP guardrail).

Problem:
Player UI kan forsøge submit før der er gyldig spillerkontekst (player_id/session_token/round_question_id/code). Det giver unødige 400-fejl og dårlig UX.

Need-to-have (MVP UI):

  • Lås Submit løgn og Submit gæt indtil join + round context er komplet.
  • Vis kort status-tekst i UI når kontekst mangler (fx “Join først”).
  • Bevar eksisterende flow for lås efter successful submit.

Acceptance:

  • Ingen submit-kald trigges fra UI når nødvendig kontekst mangler.
  • Knapper bliver automatisk aktive når kontekst er klar.
  • Eksisterende tests for player screen forbliver grønne.
Scope-kilde: #16 (epic board) + #17 (MVP guardrail). Problem: Player UI kan forsøge submit før der er gyldig spillerkontekst (player_id/session_token/round_question_id/code). Det giver unødige 400-fejl og dårlig UX. Need-to-have (MVP UI): - Lås `Submit løgn` og `Submit gæt` indtil join + round context er komplet. - Vis kort status-tekst i UI når kontekst mangler (fx “Join først”). - Bevar eksisterende flow for lås efter successful submit. Acceptance: - Ingen submit-kald trigges fra UI når nødvendig kontekst mangler. - Knapper bliver automatisk aktive når kontekst er klar. - Eksisterende tests for player screen forbliver grønne.
email-manager added the need-to-haveui labels 2026-02-28 01:03:24 +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 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#55
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?