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

MVP #175: Shared i18n keyspace + Django i18n bootstrap (da/en) #248

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

Problem: Frontend/backend mangler fælles i18n-struktur (da/en), hvilket blokerer konsistent UI/API-tekst i SPA og Django templates.

Værdi: Giver én delt key-strategi inspireret af email-manager mønsteret og reducerer regressionsrisiko i MVP.

Hvorfor nu: PO har markeret #175 som aktiv need-to-have.

Scope (PR-klar, lille bid):

  • Definér shared key-namespace konvention (fx game., lobby., errors.*).
  • Tilføj Django i18n-setup baseline for da+en (locale scaffolding, fallback-regel, dokumenteret load-path).
  • Tilføj kontraktnotat for frontend/backend key ownership.

Acceptance:

  1. Key-strategi dokumenteret i repo (og refereret fra SPA-plan).
  2. Django kan resolve da/en translations med fallback uden runtime-fejl.
  3. Eksempel-nøgler findes i både backend og frontend-kontrakt.

Afgrænsning: Ingen UI-polish, ingen fuld oversættelse af hele appen endnu.

Problem: Frontend/backend mangler fælles i18n-struktur (da/en), hvilket blokerer konsistent UI/API-tekst i SPA og Django templates. Værdi: Giver én delt key-strategi inspireret af email-manager mønsteret og reducerer regressionsrisiko i MVP. Hvorfor nu: PO har markeret #175 som aktiv need-to-have. Scope (PR-klar, lille bid): - Definér shared key-namespace konvention (fx game.*, lobby.*, errors.*). - Tilføj Django i18n-setup baseline for da+en (locale scaffolding, fallback-regel, dokumenteret load-path). - Tilføj kontraktnotat for frontend/backend key ownership. Acceptance: 1) Key-strategi dokumenteret i repo (og refereret fra SPA-plan). 2) Django kan resolve da/en translations med fallback uden runtime-fejl. 3) Eksempel-nøgler findes i både backend og frontend-kontrakt. Afgrænsning: Ingen UI-polish, ingen fuld oversættelse af hele appen endnu.
architecture-bot added the bot-taskneed-to-havei18nmvp labels 2026-03-02 02:25:50 +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 bot-task i18n mvp 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#248
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?