📝 Fix: How should logic-execution-engine.service.ts make HTTP calls...

Date: 2026-03-17
Time: 17:27:58 UTC
Session: gspace1-229.9
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should logic-execution-engine.service.ts make HTTP calls to backend API endpoints (auth/login, auth/check-permissions, email/send, payment/process, storage/upload)?

Task: Not specified

🎯 Decision Made

Chosen:

Inject API_BASE_URL from @libs-foundational/api-config and use ${this.apiUrl}/... for all 5 endpoints instead of hardcoded /api/... paths

Options Considered:

• No alternatives documented

💭 Reasoning

S229.3 convention: hardcoded proxy paths only work in dev and silently 404 in production. Injected tokens resolve to /api in dev and https://api.gograb.space/api in prod. Matches api-tools.service.ts pattern.

📁 Files Involved

• libs/libs-structural/flow-engine-lib/src/lib/services/logic-execution-engine.service.ts

🔗 Related

• Decision ID: dev_1773768477979_tg07i9q
• Session: 229
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation