Pattern: What pattern should be followed when bringing features/compo...

Documentation for Sessions

🎨 Pattern: What pattern should be followed when bringing features/compo...

Date: 2026-02-05
Time: 03:49:39 UTC
Session: editor2-89.3
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

What pattern should be followed when bringing features/components from gograb-modules monorepo to editor2 monorepo?

Task: Establishing migration pattern from gograb-modules to editor2

🎯 Decision Made

Chosen:

Audit and update all API-related code during migration

Options Considered:

Copy as-is and fix issues as they arise
Audit and update all API-related code during migration
Create a migration checklist

💭 Reasoning

gograb-modules has NO real backend - it uses mock APIs for everything. editor2 HAS a real backend-api (port 3000), backend-ai-api (port 3001), backend-docs-api (port 3002). When migrating: (1) Remove or disable mockHttpInterceptor if using real backend, (2) Update app.config.ts to use @libs-foundational/api-config with appropriate ENVIRONMENT_PRESET, (3) Ensure proxy.conf.json is configured for the app, (4) If backend is missing required endpoints, implement them in backend-api rather than keeping mocks, (5) Test auth flow specifically since @libs-core/security mocks have different response format than @auth-ui expects.

📁 Files Involved

apps/gograb-admin/src/app/app.config.ts
apps/gograb-dev/src/app/app.config.ts
libs/libs-foundational/api-config/

🔗 Related

Decision ID: dev_1770263379489_35egejs
Session: 89
Workspace: editor2

Auto-generated by MCP Smart Consolidation