bakery-admin/bakery-ia
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: Remove TEXT fields and use only reasoning_data for i18n

Browse Source 
Completed the migration to structured reasoning_data for multilingual
dashboard support. Removed hardcoded TEXT fields (reasoning, consequence)
and updated all related code to use JSONB reasoning_data.

Changes:

1. Models Updated (removed TEXT fields):
   - PurchaseOrder: Removed reasoning, consequence TEXT columns
   - ProductionBatch: Removed reasoning TEXT column
   - Both now use only reasoning_data (JSONB/JSON)

2. Dashboard Service Updated:
   - Changed to return reasoning_data instead of TEXT fields
   - Creates default reasoning_data if missing
   - PO actions: reasoning_data with type and parameters
   - Production timeline: reasoning_data for each batch

3. Unified Schemas Updated (no separate migration):
   - services/procurement/migrations/001_unified_initial_schema.py
   - services/production/migrations/001_unified_initial_schema.py
   - Removed reasoning/consequence columns from table definitions
   - Updated comments to reflect i18n approach

Database Schema:
- purchase_orders: Only reasoning_data (JSONB)
- production_batches: Only reasoning_data (JSON)

Backend now generates:
{
  "type": "low_stock_detection",
  "parameters": {
    "supplier_name": "Harinas del Norte",
    "days_until_stockout": 3,
    ...
  },
  "consequence": {
    "type": "stockout_risk",
    "severity": "high"
  }
}

Next Steps:
- Frontend: Create i18n translation keys
- Frontend: Update components to translate reasoning_data
- Test multilingual support (ES, EN, CA)
This commit is contained in:
Claude
2025-11-07 18:20:05 +00:00
parent ddc4928d78
commit f74b8d5402
5 changed files with 75 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
services/procurement/migrations/versions/001_unified_initial_schema.py
View File

@@ -6,7 +6,7 @@ Create Date: 2025-11-07
Complete procurement service schema including:
- Procurement plans and requirements
- Purchase orders and items (with reasoning fields for JTBD dashboard)
- Purchase orders and items (with reasoning_data for i18n JTBD dashboard)
- Deliveries and delivery items
- Supplier invoices
- Replenishment planning
@@ -207,7 +207,7 @@ def upgrade() -> None:
# PURCHASE ORDER TABLES
# ========================================================================
# Create purchase_orders table (with JTBD dashboard reasoning fields)
# Create purchase_orders table (with reasoning_data for i18n)
op.create_table('purchase_orders',
sa.Column('id', postgresql.UUID(as_uuid=True), nullable=False),
sa.Column('tenant_id', postgresql.UUID(as_uuid=True), nullable=False),
@@ -242,9 +242,7 @@ def upgrade() -> None:
sa.Column('notes', sa.Text(), nullable=True),
sa.Column('internal_notes', sa.Text(), nullable=True),
sa.Column('terms_and_conditions', sa.Text(), nullable=True),
# JTBD Dashboard fields
sa.Column('reasoning', sa.Text(), nullable=True),
sa.Column('consequence', sa.Text(), nullable=True),
# JTBD Dashboard: Structured reasoning for i18n support
sa.Column('reasoning_data', postgresql.JSONB(astext_type=sa.Text()), nullable=True),
sa.Column('created_at', sa.DateTime(timezone=True), server_default=sa.text('now()'), nullable=False),
sa.Column('updated_at', sa.DateTime(timezone=True), server_default=sa.text('now()'), onupdate=sa.text('now()'), nullable=False),