Files

beabigegg ed8d30e9bd spec: add proposals for debug logging cleanup and i18n completion

Two new proposals from comprehensive QA review:

1. cleanup-debug-logging
   - Remove 60+ console.log/error statements from frontend
   - Create environment-aware logging utility
   - Prevent sensitive data exposure in browser console

2. complete-i18n-coverage
   - Add missing translations to WeeklyReportPreview
   - Add missing translations to ReportHistory
   - Add missing translations to AuditPage modal
   - Use dynamic locale for date formatting

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-13 21:28:27 +08:00

1.1 KiB

Raw Blame History

Complete i18n Coverage

Problem Statement

Several frontend components contain hardcoded English strings that are not internationalized. This breaks the multi-language support for users who prefer Chinese (Traditional) or other locales.

Affected Components

WeeklyReportPreview.tsx (~20 hardcoded strings)
- Report labels, status names, error messages
- Date formatting uses hardcoded locale
ReportHistory.tsx (~10 hardcoded strings)
- History labels, loading states, empty states
AuditPage.tsx (~30 hardcoded strings in modal)
- Detail modal labels, verification modal text
- Field names, status messages
WorkloadPage.tsx (1 hardcoded error message)

Proposed Solution

Add all missing translation keys to locale files
Replace hardcoded strings with t() function calls
Use dynamic locale for date formatting based on i18n.language

Success Criteria

All user-visible strings use i18n translation keys
Both en/common.json and zh-TW/common.json contain all keys
Date/time formatting respects user's language preference
Frontend builds and functions correctly

1.1 KiB Raw Blame History