Skip to content

GDPR/KVKK data-export screen ships hardcoded English strings (no EN/TR i18n) #100

Description

@ahmetabdullahgultekin

Why: The mobile 'Export my data' GDPR/KVKK screen renders hardcoded English literals instead of going through the StringKey/t() i18n table, violating the platform no-hardcoded-strings + EN/TR coverage rule. The placeholder keys point at a throwaway scratch file (/tmp/i18n_agent_20B.txt) that no longer exists, so the keys were never added.

Done when: DATA_EXPORT_* StringKey entries exist in both the EN and TR maps and all five sites consume them via the resource lookup (no literal English remains).

Affected sites:

  • androidApp/.../ui/component/ExportDataRow.kt:56 (title/description/in-progress/share-sheet literals)
  • androidApp/.../ui/component/ExportDataRow.kt:145
  • androidApp/.../ui/component/ExportDataRow.kt:154
  • androidApp/.../ui/viewmodel/DataExportViewModel.kt:84
  • androidApp/.../ui/viewmodel/DataExportViewModel.kt:94

source: androidApp/src/main/kotlin/com/fivucsas/mobile/android/ui/component/ExportDataRow.kt:56


Migrated from androidApp/src/main/kotlin/com/fivucsas/mobile/android/ui/component/ExportDataRow.kt:56.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions