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

[MVP][READY] Angular-first: host+player i18n integration uden React #222

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

Problem

  • SPA-flowet skal være Angular-first; i18n i host+player skal kobles på shared keys uden React-afhængighed.

Værdi

  • Holder migrationsspor konsistent og reducerer leverancerisiko.

Hvorfor nu

  • PO-direktiv: Angular-first for host+player; React kun fallback ved dokumenteret blokering.

Scope (lille PR)

  • Integrér i18n-service i Angular app-shell for host/player routes.
  • Wire locale-load fra backend endpoint/context.
  • Erstat hardcodede kerne-UI-strenge i host/player med keys i kerneflow.

Acceptance

  • Host og player viser da/en via shared keys i kerneflow.
  • Ingen React-kode tilføjes i denne PR.
  • Hvis blocker opdages, dokumenteres den i PR med konkret evidens.
Problem - SPA-flowet skal være Angular-first; i18n i host+player skal kobles på shared keys uden React-afhængighed. Værdi - Holder migrationsspor konsistent og reducerer leverancerisiko. Hvorfor nu - PO-direktiv: Angular-first for host+player; React kun fallback ved dokumenteret blokering. Scope (lille PR) - Integrér i18n-service i Angular app-shell for host/player routes. - Wire locale-load fra backend endpoint/context. - Erstat hardcodede kerne-UI-strenge i host/player med keys i kerneflow. Acceptance - Host og player viser da/en via shared keys i kerneflow. - Ingen React-kode tilføjes i denne PR. - Hvis blocker opdages, dokumenteres den i PR med konkret evidens.
architecture-bot added the bot-taskneed-to-havearchitecti18nfrontendbackend labels 2026-03-01 22:48:00 +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 backend bot-task frontend i18n need-to-have
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#222
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?