Implementation: Should we silence debug utilities that spam console on app l...

Documentation for Sessions

⚙️ Implementation: Should we silence debug utilities that spam console on app l...

📋 Decision Context

Question:

Should we silence debug utilities that spam console on app load?

Task: Not specified

🎯 Decision Made

Chosen:

Silence debug utilities - only log when explicitly called

Options Considered:

Keep logging on import
Silence completely
Migrate to createLogger
Remove utilities

💭 Reasoning

Debug utilities were generating 10 logs on every app load just to announce they're available. This is pure noise. Solution: Keep utilities available on window object but don't log on import. Added showDebugUtils() helper function that users can call to see available functions. Result: 10 logs → 0 logs (100% reduction) while maintaining full functionality. Users can still access all debug functions via window object, they just don't get spammed about it on every page load.

📁 Files Involved

apps/gograb-space/src/app/utils/debug-sync-verification.ts
libs/libs-foundational/core-angular/src/lib/utils/debug-universe-storage.ts
apps/gograb-space/src/app/utils/clear-cached-space.ts

🔗 Related

Decision ID: dev_1767731671580_x6zukag
Session: 22
Workspace: editor2

Auto-generated by MCP Smart Consolidation