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

[READY][i18n][P17] Django i18n foundation: locale pipeline + resolver for shared keys (da/en) #205

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

Problem:
Backend mangler MVP-sikker foundation for at kunne levere locale-konsistente responses efter den delte kontrakt i #175.

Værdi:
Gør backend i stand til stabil en fallback + da/en output, så frontend og API ikke divergerer.

Hvorfor nu:
Need-to-have i #175 kan ikke lukkes uden backend-fundament.

Acceptance:

  • Django i18n setup verificeret for en + da (locale loading + fallback til en).
  • Shared-key resolver/adapter i backend følger kontrakten (ingen ad hoc strengmapping).
  • Mindst ét repræsentativt API-svar/fejlflow dokumenteret med key/locale-opførsel.
  • Manglende key håndteres deterministisk og logbart (ingen silent failure).

Afgrænsning:

  • Ingen frontend rendering i denne opgave.
  • Ingen udvidelse til ekstra sprog ud over da/en.
Problem: Backend mangler MVP-sikker foundation for at kunne levere locale-konsistente responses efter den delte kontrakt i #175. Værdi: Gør backend i stand til stabil `en` fallback + `da/en` output, så frontend og API ikke divergerer. Hvorfor nu: Need-to-have i #175 kan ikke lukkes uden backend-fundament. Acceptance: - Django i18n setup verificeret for `en` + `da` (locale loading + fallback til `en`). - Shared-key resolver/adapter i backend følger kontrakten (ingen ad hoc strengmapping). - Mindst ét repræsentativt API-svar/fejlflow dokumenteret med key/locale-opførsel. - Manglende key håndteres deterministisk og logbart (ingen silent failure). Afgrænsning: - Ingen frontend rendering i denne opgave. - Ingen udvidelse til ekstra sprog ud over da/en.
architecture-bot added the bot-taskneed-to-havearchitecti18nbackend labels 2026-03-01 19:32:28 +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 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#205
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?