Implementation: How should we continue reducing excessive console logs after...

Documentation for Sessions

⚙️ Implementation: How should we continue reducing excessive console logs after...

📋 Decision Context

Question:

How should we continue reducing excessive console logs after initial migration?

Task: Not specified

🎯 Decision Made

Chosen:

Continue systematic migration of remaining high-volume sources

Options Considered:

Stop migration
Migrate only critical services
Continue systematic migration
Disable all logs

💭 Reasoning

Continued migration of high-volume log sources: auth.mock.ts (11 logs), space-map-flash-state.service.ts (44 logs - biggest impact!), network-sync-state.service.ts (12 logs), providers.ts (3 logs), core-widgets.ts (1 log). All migrated to createLogger with appropriate categories (init, flash, sync, theme, widgets). AuthMock endpoint loading log disabled by default (too verbose). Result: ~70 logs migrated in this batch, bringing total reduction to ~75% (330 → ~80 logs remaining). Pattern proven and consistent across all services.

📁 Files Involved

libs/core/mock-api/src/mocks/auth.mock.ts
libs/theme-system/theme-runtime/src/lib/providers/providers.ts
libs/libs-widgets/widgets/src/lib/core-widgets.ts
libs/libs-structural/space-map-lib/src/lib/services/space-map-flash-state.service.ts
libs/libs-foundational/storage-system/src/sync/services/network-sync-state.service.ts

🔗 Related

Decision ID: dev_1767732970848_h0k9fq6
Session: 22
Workspace: editor2

Auto-generated by MCP Smart Consolidation