⚙️ Implementation: How should we continue the logging migration to achieve clea...

📋 Decision Context

Question:

How should we continue the logging migration to achieve clean, organized console output?

Task: Continue Session 26.3 - Centralized Logging Migration

🎯 Decision Made

Chosen:

Continue systematic migration focusing on theme services and high-volume sources from user's console output

Options Considered:

1. Continue systematic migration of remaining high-volume services
2. Focus only on theme services
3. Stop migration and enable all logs
4. Remove all console.log statements

💭 Reasoning

Based on session-22 documentation and session-26 progress, we've successfully migrated ~47% of logs with proven pattern. User's console shows ~100+ logs on page load, primarily from: theme services (theme-variables, theme-application, simple-theme-storage), auth services, icon system, and various initialization logs. Theme services have 187 console.log statements across 35 files - highest priority. Will use established createLogger pattern with appropriate categories, keep only essential logs short and concise, and maintain runtime control via LogControl. This approach provides clean console by default while preserving debugging capability.

📁 Files Involved

• libs/theme-system/theme-runtime/src/lib/services/*.ts
• libs/libs-foundational/core-angular/src/lib/services/auth.service.ts
• libs/libs-ui/icon-system/src/lib/services/icon.service.ts

🔗 Related

• Decision ID: dev_1767736884261_pkpofs1
• Session: 22
• Workspace: editor2

Auto-generated by MCP Smart Consolidation