🐛 Bugfix: Why did the extension panel render with blank/empty content ...

Date: 2026-02-11
Time: 15:16:07 UTC
Session: gspace1-105.9
Agent: angular
Confidence: 100%
Status: ✅ Documented

📋 Decision Context

Question:

Why did the extension panel render with blank/empty content after the iframe successfully loaded (port issue fixed)?

Task: Session 105.3: Fix blank panel content — NG0201 missing LOGGER_CONFIG provider

🎯 Decision Made

Chosen:

Added provideLogSystem() with ConsoleAppender to gograb-ai app.config.ts. The NG0201 error (No provider for LOGGER_CONFIG) crashed the AIPanelComponent before it could render. All other apps (gograb-space, gograb-admin, gograb-dev) already had this provider.

Options Considered:

1. Add provideLogSystem() to app.config.ts (global)
2. Add providers to the panel route definition
3. Make LoggerService use optional injection for LOGGER_CONFIG

💭 Reasoning

The dependency chain was: ExtensionPanelComponent -> AIPanelComponent -> ModuleGeneratorService -> LoggerService -> LOGGER_CONFIG. LoggerService uses inject(LOGGER_CONFIG) which is NOT optional — it throws NG0201 if missing. The gograb-ai app was created as a minimal skeleton (MVP Phase 0.1) and never received the logging provider that all other apps have. Adding it at the app.config.ts level (global) is correct because LoggerService is used throughout the component tree, not just in the panel route. The configuration mirrors other apps: debug level in dev mode, ConsoleAppender, performance metrics enabled in dev.

📁 Files Involved

• apps/gograb-ai/src/app/app.config.ts

🔗 Related

• Decision ID: dev_1770822967216_0ljboy1
• Session: 105
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation