MS-BE-API-5: i18n und Consent implementieren #100
Labels
No labels
component/backend
component/docs
component/e2e
component/frontend
component/infra
component/keycloak
prio/high
prio/low
prio/medium
type/bug
type/chore
type/feature
type/refactor
type/test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
WompSchmiede/FamilienFeierPlaner#100
Loading…
Add table
Add a link
Reference in a new issue
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?
Aufgaben
i18n-Strategie: Dateien liegen im Frontend (frontend/src/lib/i18n/{lang}/*.json), kategorisiert nach Bereichen (events.json, persons.json usw.). Verwaltung per Code-Change.
Siehe docs/design.md �2 (consents) und �2 (i18n).