🏗️ Architecture: How to resolve conflicting GeneratedModule types between mod...

Date: 2026-01-22
Time: 03:29:58 UTC
Session: editor2-54.5
Agent: angular
Confidence: 85%
Status: ✅ Documented

📋 Decision Context

Question:

How to resolve conflicting GeneratedModule types between module-schema.model.ts and module-generation.types.ts?

Task: Not specified

🎯 Decision Made

Chosen:

Define local interfaces in consuming components

Options Considered:

1. Unify types into single definition
2. Define local interfaces in consuming components
3. Create adapter layer
4. Use type aliases with renames

💭 Reasoning

The codebase has two incompatible GeneratedModule definitions that evolved separately: one in module-schema.model.ts (used by services) and one in module-generation.types.ts (legacy alias for GeneratedCodeModule). Rather than refactoring the entire type system mid-session, defined minimal local interfaces in ai-panel.component.ts with required properties and used type casts. This is a pragmatic fix that allows the app to run while a proper type unification can be planned.

📁 Files Involved

• libs/libs-ai/vitto-hub/src/lib/components/ai-panel/ai-panel.component.ts
• libs/libs-ai/module-generator/src/lib/models/module-schema.model.ts
• libs/libs-ai/module-generator/src/lib/types/module-generation.types.ts

🔗 Related

• Decision ID: dev_1769052598069_z32sgwt
• Session: 54
• Workspace: editor2

Auto-generated by MCP Smart Consolidation