i18n scaffold with i18next (de/en) and missing-key CI check #5
Labels
No Label
area:auth
area:docs
area:export
area:ops
area:storage
area:supply-chain
auth
backend
blocked
collab
deployment
docs
effort:L
effort:M
effort:S
frontend
plugins
qa
vs-nfd
vs-nfd:blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: stwaidele/dorfteich#5
Loading…
Reference in New Issue
Block a user
No description provided.
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?
Context
ADR 0012: every UI string goes through i18n from the start; retrofitting is expensive.
Scope
Set up i18next + react-i18next in
apps/web(language detection: user setting later,Accept-Languagenow,enfallback) and a minimal i18next instance inapps/apifor error messages/mails. Resources live inpackages/shared/i18n/<lang>/<ns>.jsonwithdeanden. Convert all strings from #4 to keys. Add a CI-runnable scripti18n:checkthat fails on keys missing in either language.Acceptance criteria
?lng=de|enand renders both languages on the shellpnpm i18n:checkfails when a key exists inenbut notde(prove with a test)code; the web client renders the localized messageTechnical notes
common,auth,errors.Dependencies
Depends on #2, #4.
Size: ~1 day
Conventions: English code/comments, clear human-readable code, no hard-coded UI strings (ADR 0012, add
deanden), permission checks only via the shared guard (docs/architecture/permissions.md). Read the referenced ADRs before starting.