Architecture: Where should SpaceExplorerComponent live in the codebase?
Documentation for Sessions
🏗️ Architecture: Where should SpaceExplorerComponent live in the codebase?
📋 Decision Context
Question:
Where should SpaceExplorerComponent live in the codebase?
Task: Session 45.8: Create space-explorer as independent NX library
🎯 Decision Made
Chosen:
Created new independent @libs-space/space-explorer NX library
Options Considered:
- No alternatives documented
💭 Reasoning
A Space is architecturally a layer ABOVE Universe in the hierarchy (Space → Universe → Galaxy → World → Page). Therefore, space-level components should NOT be inside universe-canvas. Creating a dedicated space-explorer library maintains proper architectural boundaries and separation of concerns. The user explicitly noted 'this is common sense' regarding this layering.
📁 Files Involved
libs/libs-space/space-explorer/libs/libs-space/universe-canvas/apps/gograb-space/src/app/app.routes.ts
🔗 Related
- Decision ID:
dev_1768497333690_vxvy8dp - Session: 45
- Workspace: editor2
Auto-generated by MCP Smart Consolidation