🏗️ Architecture: What should the Vitto Studio code editor file tree show vs n...

Date: 2026-03-17
Time: 21:23:44 UTC
Session: gspace1-231.5
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

What should the Vitto Studio code editor file tree show vs not show? What constitutes 'the app' from a user perspective?

Task: Fix Vitto Studio file tree UX — show app shell, remove JSON noise

🎯 Decision Made

Chosen:

Code editor VFS shows only: app/ (Angular app shell from GitLab apps/ dir), modules/ (TypeScript/HTML/SCSS from GitLab), config/ (manifest.json), docs/ (README). Pages/widgets/entities JSON blobs removed — those are data management, handled by dedicated dock panels (Entities, Data).

Options Considered:

• No alternatives documented

💭 Reasoning

The apps/ directory (app.component.ts, app.routes.ts, app.config.ts, main.ts) IS the app the user couldn't see — it was never loaded from GitLab. Pages/widgets/entities are database records serialized to JSON, not code a developer edits. Showing them in the code tree confuses intent — users expect TypeScript/HTML/SCSS, not raw data blobs. Dedicated panels (Data browser, Entity designer) handle those data concerns.

📁 Files Involved

• libs/libs-structural/vitto-studio/src/lib/services/vfs-sync.service.ts
• APIs/backend-ai-api/src/app/module-files/studio-repo.controller.ts

🔗 Related

• Decision ID: dev_1773782624737_nimjm13
• Session: 231
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation