From 071cba2ef9d9e781bdebab76b9beb1e885f8d0c7 Mon Sep 17 00:00:00 2001 From: Zoe Forbes Date: Sun, 1 Feb 2026 14:24:35 -0600 Subject: [PATCH] fix: include parent_part_number in BOM API response BOMEntryResponse was missing the ParentPartNumber field. The database query populates it correctly, but the API serialization dropped it. This caused the Calc extension to never populate the hidden _silo_parent_pn column during pull, so push never called _update_bom_relationship and no BOM entries were created. --- internal/api/bom_handlers.go | 2 ++ 1 file changed, 2 insertions(+) diff --git a/internal/api/bom_handlers.go b/internal/api/bom_handlers.go index e9d7315..119d6c3 100644 --- a/internal/api/bom_handlers.go +++ b/internal/api/bom_handlers.go @@ -19,6 +19,7 @@ import ( // BOMEntryResponse represents a BOM entry in API responses. type BOMEntryResponse struct { ID string `json:"id"` + ParentPartNumber string `json:"parent_part_number"` ChildPartNumber string `json:"child_part_number"` ChildDescription string `json:"child_description"` RelType string `json:"rel_type"` @@ -424,6 +425,7 @@ func bomEntryToResponse(e *db.BOMEntry) BOMEntryResponse { } return BOMEntryResponse{ ID: e.RelationshipID, + ParentPartNumber: e.ParentPartNumber, ChildPartNumber: e.ChildPartNumber, ChildDescription: e.ChildDescription, RelType: e.RelType,