Marc-André Bombeck 8dced00188 feat(medications): label each intake history row with its logging origin ...

The intake history surfaced the coarse IntakeSource enum directly, so a
dose logged from the iOS app showed nothing meaningful. Map the enum to
the practical client it represents — WEB to Web, API to iOS App,
REMINDER to Reminder, IMPORT to Import — and render it as a muted
"via {origin}" caption on each intake row next to the status. No schema
or API change; the source value already rides the existing intake
response. Tighten the en/de labels that read "External API" and
"Telegram / Reminder" into the same origin vocabulary across all six
locales.

2026-06-01 17:31:02 +02:00

..

de.json

feat(medications): label each intake history row with its logging origin

2026-06-01 17:31:02 +02:00

en.json

feat(medications): label each intake history row with its logging origin

2026-06-01 17:31:02 +02:00

es.json

feat(medications): label each intake history row with its logging origin

2026-06-01 17:31:02 +02:00

fr.json

feat(medications): label each intake history row with its logging origin

2026-06-01 17:31:02 +02:00

it.json

feat(medications): label each intake history row with its logging origin

2026-06-01 17:31:02 +02:00

pl.json

feat(medications): label each intake history row with its logging origin

2026-06-01 17:31:02 +02:00