Bugfix: Generated app routes use wrong relative import depth (3 leve...
Documentation for Sessions
🐛 Bugfix: Generated app routes use wrong relative import depth (3 leve...
Date: 2026-03-17
Time: 16:11:31 UTC
Session: gspace1-230.6
Agent: angular
Confidence: 98%
Status: ✅ Documented
📋 Decision Context
Question:
Generated app routes use wrong relative import depth (3 levels instead of 4)
Task: S230: Fix remaining generation pipeline gaps
🎯 Decision Made
Chosen:
Fixed app-shell-generator.service.ts: changed ../../../modules/ to ../../../../modules/ in route imports. From apps/{slug}/src/app/app.routes.ts, 4 '../' are needed to reach repo root, not 3.
Options Considered:
- No alternatives documented
💭 Reasoning
apps/{slug}/src/app/ → ../ src/ → ../../ apps/{slug}/ → ../../../ apps/ → ../../../../ root/. With 3 levels, the import resolved to apps/modules/ which doesn't exist. The generated platforms would fail at ng build with 'module not found' errors. This only affects the actual Angular CLI build — the rspack/WASM preview synthesizes its own app shell so it was never affected.
📁 Files Involved
APIs/backend-vitto-api/src/app/module-generation/generators/app-shell-generator.service.ts
🔗 Related
- Decision ID:
dev_1773763891360_2d9v885 - Session: 230
- Workspace: gspace1
Auto-generated by MCP Smart Consolidation