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

📋 Decision Context

Question:

How should we reduce console noise from ModuleRegistryService and EventBusService?

Task: Continue logging migration - reduce noise from ModuleRegistryService and EventBusService

🎯 Decision Made

Chosen:

Migrate to createLogger from @libs-dev-tools/debug-utils and remove verbose logs

Options Considered:

1. Keep LoggerService but increase minimum log level
2. Migrate to createLogger from @libs-dev-tools/debug-utils and remove verbose logs
3. Disable all logs in these services
4. Use LoggerService but remove console.log statements

💭 Reasoning

ModuleRegistryService and EventBusService were generating excessive console logs (50+ logs per module registration). Migrated both to centralized logging system (createLogger from @libs-dev-tools/debug-utils). ModuleRegistryService: Removed all console.log statements and verbose logger.debug/info calls, keeping only error logs. EventBusService: Removed console.info logging for every event publication (was controlled by enableLogging config), now only logs errors. Both services now use 'modules' and 'debug' categories respectively, allowing category-based control via LOG_CONFIG. This reduces noise from 50+ logs per operation to 0 logs (errors only when they occur).

📁 Files Involved

• libs/core/module-base/src/lib/services/module-registry.service.ts
• libs/core/event-system/src/lib/services/event-bus.service.ts

🔗 Related

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

Auto-generated by MCP Smart Consolidation