📝 Fix: Complete list of files with hardcoded /api paths that needed...

Date: 2026-01-28
Time: 15:33:49 UTC
Session: editor2-72.76
Agent: angular
Confidence: 100%
Status: ✅ Documented

📋 Decision Context

Question:

Complete list of files with hardcoded /api paths that needed fixing for production deployment

Task: Not specified

🎯 Decision Made

Chosen:

Fixed all 11 files total: widgets-api.service.ts, widget-promotion.service.ts, module-export.service.ts, module-creation-wizard.component.ts, flow-picker-modal.component.ts, flow-attacher.component.ts, universal-asset-registry.service.ts, billing-dashboard.component.ts, space-map-analytics.service.ts, building-blocks-library.component.ts, building-blocks-embeddable.component.ts. All now use inject(API_BASE_URL) from @libs-foundational/core-angular.

Options Considered:

• No alternatives documented

💭 Reasoning

Each file was using hardcoded relative /api URLs which worked in development (due to proxy config) but failed in production because they resolved to app.gograb.space/api instead of api.gograb.space/api. The API_BASE_URL injection token is provided in app.config.ts with environment.backendApiUrl value, ensuring correct URLs in all environments. No circular dependency issues because all modified libraries (libs-widgets, libs-structural, libs-module-utils, libs-ai) can safely import from libs-foundational.

📁 Files Involved

• No files specified

🔗 Related

• Decision ID: dev_1769614425742_awjstpy
• Session: 72
• Workspace: editor2

Auto-generated by MCP Smart Consolidation