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

[READY][SPA][P1] Angular app-shell + host/player routing skeleton #157

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

Problem
Nuværende UI er template+inline JS, så SPA-migration kan ikke starte uden et stabilt shell med routing.

Værdi
Etablerer fundament for parallel udvikling af host/player-flow uden at ændre backend-kontrakter.

Hvorfor nu
PO-direktiv har aktiveret SPA-migrationsspor (Angular-first). Uden shell/routing står hele migrationskøen stille.

Acceptance

  • frontend/ Angular app oprettet og kan buildes lokalt.
  • Router har mindst ruterne /host og /player med placeholder views.
  • Django kan servere/indlejre app-shell bag feature-flag (ingen default-cutover).
  • Ingen ændring af eksisterende API-endpoints.

Afgrænsning

  • Ingen gameplay-logik.
  • Ingen styling-polish ud over minimal layout-struktur.
  • Ingen backend-kontraktændringer.

Labels

  • bot-task
  • need-to-have
  • architect
  • ui
Problem Nuværende UI er template+inline JS, så SPA-migration kan ikke starte uden et stabilt shell med routing. Værdi Etablerer fundament for parallel udvikling af host/player-flow uden at ændre backend-kontrakter. Hvorfor nu PO-direktiv har aktiveret SPA-migrationsspor (Angular-first). Uden shell/routing står hele migrationskøen stille. Acceptance - `frontend/` Angular app oprettet og kan buildes lokalt. - Router har mindst ruterne `/host` og `/player` med placeholder views. - Django kan servere/indlejre app-shell bag feature-flag (ingen default-cutover). - Ingen ændring af eksisterende API-endpoints. Afgrænsning - Ingen gameplay-logik. - Ingen styling-polish ud over minimal layout-struktur. - Ingen backend-kontraktændringer. Labels - bot-task - need-to-have - architect - ui
architecture-bot added the bot-taskneed-to-havearchitectui labels 2026-03-01 11:54:43 +01:00
dev-bot commented 2026-03-01 12:07:19 +01:00
Owner
Copy Link

Dev-runner status: Implementation for Angular app-shell + host/player routing is complete locally on branch dev/issue-157-angular-shell-v2 (3 commits), and local checks passed (npm run build in frontend/angular, .venv/bin/python manage.py test lobby.tests.UiScreenTests).

Blocker: Cannot push branch from this runner because SSH auth is unavailable and Gitea rejects HTTP git push (Interacting with repositories by HTTP protocol is not allowed, 403).

Next action: Provide SSH key access for this runner (or alternative allowed push transport), then run: git push origin dev/issue-157-angular-shell-v2 and open PR to main.

Dev-runner status: Implementation for Angular app-shell + host/player routing is complete locally on branch `dev/issue-157-angular-shell-v2` (3 commits), and local checks passed (`npm run build` in `frontend/angular`, `.venv/bin/python manage.py test lobby.tests.UiScreenTests`). **Blocker:** Cannot push branch from this runner because SSH auth is unavailable and Gitea rejects HTTP git push (`Interacting with repositories by HTTP protocol is not allowed`, 403). **Next action:** Provide SSH key access for this runner (or alternative allowed push transport), then run: `git push origin dev/issue-157-angular-shell-v2` and open PR to `main`.
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#157
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?