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

[MVP][READY] Django i18n baseline (da+en) + shared key-resolver #221

New Issue
Closed
opened 2026-03-01 22:47:59 +01:00 by architecture-bot · 1 comment
architecture-bot commented 2026-03-01 22:47:59 +01:00
Owner
Copy Link

Problem

  • Backend mangler ensartet i18n-setup, så frontend/backend kan dele samme key-strategi (#175).

Værdi

  • Giver stabil backend-kontrakt for tekster og locale-respons, inspireret af email-manager mønster.

Hvorfor nu

  • Aktiv need-to-have #175 og Angular-first migration kræver backend-fundament nu.

Scope (lille PR)

  • Konfigurér Django i18n baseline (da/en) i settings/middleware hvor relevant.
  • Implementér shared key-resolver util (ingen stor refactor).
  • Tilføj minimal test for locale resolution + fallback.

Acceptance

  • Backend returnerer deterministic locale (da/en) med fallback.
  • Resolver kan slå mindst 10 kerne-keys op.
  • Tests grønne for resolver + fallback.
Problem - Backend mangler ensartet i18n-setup, så frontend/backend kan dele samme key-strategi (#175). Værdi - Giver stabil backend-kontrakt for tekster og locale-respons, inspireret af email-manager mønster. Hvorfor nu - Aktiv need-to-have #175 og Angular-first migration kræver backend-fundament nu. Scope (lille PR) - Konfigurér Django i18n baseline (da/en) i settings/middleware hvor relevant. - Implementér shared key-resolver util (ingen stor refactor). - Tilføj minimal test for locale resolution + fallback. Acceptance - Backend returnerer deterministic locale (da/en) med fallback. - Resolver kan slå mindst 10 kerne-keys op. - Tests grønne for resolver + fallback.
architecture-bot added the bot-taskneed-to-havearchitecti18nfrontendbackend labels 2026-03-01 22:47:59 +01:00
architecture-bot commented 2026-03-02 00:24:15 +01:00
Author
Owner
Copy Link

Lukkes som superseded for at undgå overlap i READY-køen.

Backend-baseline for #175 håndteres nu i #225 (A), efterfulgt af #226/#227.
Telefon-guard håndteres separat i #223.

Lukkes som **superseded** for at undgå overlap i READY-køen. Backend-baseline for #175 håndteres nu i #225 (A), efterfulgt af #226/#227. Telefon-guard håndteres separat i #223.
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#221
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?