egg/PROJECT-CONTORL
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
ed8d30e9bd0b28190a9f67d4354a9c3bba1087bb
PROJECT-CONTORL/openspec/changes/cleanup-debug-logging/proposal.md
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

Cleanup Debug Logging

Problem Statement

The frontend codebase contains 60+ console.log and console.error statements scattered across components. These debug statements:

  1. May expose sensitive information (tokens, user data, API responses) in browser console
  2. Clutter the browser console in production
  3. Impact performance from excessive logging
  4. Present an unprofessional appearance to users who open developer tools

Proposed Solution

  1. Remove all unnecessary console.log/console.error statements
  2. For essential logging, implement environment-aware logging that only outputs in development
  3. Create a centralized logging utility that respects environment settings

Affected Components

Key files with debug logging:

  • contexts/NotificationContext.tsx - WebSocket event logging
  • contexts/ProjectSyncContext.tsx - Debug logging functions
  • components/GanttChart.tsx - Progress change logging
  • Multiple other components with error logging

Success Criteria

  • No console.log statements in production build output
  • Essential error logging preserved with environment checks
  • All frontend tests continue to pass