🐛 Bugfix: Why does the generation pipeline produce 'childs' instead of...

Date: 2026-03-17
Time: 17:05:43 UTC
Session: gspace1-230.10
Agent: backend
Confidence: 98%
Status: ✅ Documented

📋 Decision Context

Question:

Why does the generation pipeline produce 'childs' instead of 'children' for collection names?

Task: Not specified

🎯 Decision Made

Chosen:

Replace all naive entitySlug + 's' pluralization with the existing pluralize() utility from pluralize.util.ts, which handles irregular plurals (child→children, person→people, etc.). Fixed in 3 locations: BackendSetupPhaseService.toCollectionName(), inline widget collectionName in createPages(), and applyApiCorrections() auto-correction strategy.

Options Considered:

• No alternatives documented

💭 Reasoning

The pluralize.util.ts already existed with correct irregular plurals map but was only used in template-generator.service.ts. The backend-setup.phase.ts and api-corrections.strategy.ts were using naive +s concatenation, producing 'childs', 'persons', etc. This is a silent data integrity bug — the LLM generates 'childs' and the auto-correction 'fixes' it to 'childs' again because it uses the same naive pluralization.

📁 Files Involved

• APIs/backend-vitto-api/src/app/module-generation/phases/backend-setup.phase.ts
• APIs/backend-vitto-api/src/app/module-generation/validation/corrections/strategies/api-corrections.strategy.ts
• APIs/backend-vitto-api/src/app/module-generation/utils/pluralize.util.ts

🔗 Related

• Decision ID: dev_1773767143875_v2l1bl7
• Session: 230
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation