📝 [Web] Translate CreateFixRequestPanel
Description
Follow-up to #292. The "Submit a fix" flow off ReportPanel (frontend/src/components/CreateFixRequestPanel.jsx) is untouched , header, helper text, photo-upload labels, validation errors, action buttons, and success/failure toasts all still render in English regardless of the active language.
Feature / Task Details
- Sweep visible strings in
CreateFixRequestPanel.jsx and replace with t() calls.
- Add a
createFix.* namespace to en.json and tr.json (or extend report.* since the panel is launched from ReportPanel , either grouping is fine).
- File-validation messages ("Only JPEG/PNG…", "File too large…") need keys too.
- Skip Nominatim/backend-generated content; only translate strings authored client-side.
Deliverables
- Updated
frontend/src/components/CreateFixRequestPanel.jsx
- Updated
frontend/src/i18n/locales/en.json and tr.json
- Existing tests should keep passing (assertions on EN literals continue to match via the JSON values).
Acceptance Criteria
📝 [Web] Translate CreateFixRequestPanel
Description
Follow-up to #292. The "Submit a fix" flow off
ReportPanel(frontend/src/components/CreateFixRequestPanel.jsx) is untouched , header, helper text, photo-upload labels, validation errors, action buttons, and success/failure toasts all still render in English regardless of the active language.Feature / Task Details
CreateFixRequestPanel.jsxand replace witht()calls.createFix.*namespace toen.jsonandtr.json(or extendreport.*since the panel is launched from ReportPanel , either grouping is fine).Deliverables
frontend/src/components/CreateFixRequestPanel.jsxfrontend/src/i18n/locales/en.jsonandtr.jsonAcceptance Criteria