⚙️ Implementation: How should we reduce console noise from ModuleWidgetBridgeSe...

📋 Decision Context

Question:

How should we reduce console noise from ModuleWidgetBridgeService logging?

Task: Continue logging control system migration - reduce noise in ModuleWidgetBridgeService

🎯 Decision Made

Chosen:

Migrate to createLogger from @libs-dev-tools/debug-utils with minimal logs

Options Considered:

1. Keep LoggerService but increase minimum log level
2. Migrate to createLogger from @libs-dev-tools/debug-utils with minimal logs
3. Disable all logs in ModuleWidgetBridgeService
4. Use LoggerService but remove trace/debug calls

💭 Reasoning

ModuleWidgetBridgeService was generating 50+ logs per sync operation using LoggerService with trace/debug levels. Migrated to centralized logging system (createLogger from @libs-dev-tools/debug-utils) using 'widgets' category. Removed all trace/debug logs, keeping only essential logs: INFO for milestones (sync completion summary) and ERROR for failures. This reduces console noise from 50+ logs to 1-2 logs per operation while maintaining category-based control via LOG_CONFIG. Users can enable/disable via LogControl.enable('widgets') in browser console.

📁 Files Involved

• libs/core/module-adapter/src/lib/module-widget-bridge.service.ts

🔗 Related

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

Auto-generated by MCP Smart Consolidation