Oliver/gmal-scope-builder
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix deep extraction crash: unescaped curly braces in f-string

Browse source 
Root cause: "name 'name' is not defined" error on line 300
The f-string example {name:"KV 360", tier:"Tier B"} was interpreted
as Python set literal, not as JSON text. Changed to parentheses.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
DJP 2026-04-13 13:23:25 -04:00
parent c49f83a5a2
commit 06bb1b9bfd
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
backend/app/services/doc_parser.py
View file

@ -297,7 +297,7 @@ STRUCTURAL ANALYSIS:
IMPORTANT GUIDELINES:
- Use the column mapping from the analysis to identify asset names, descriptions, tiers, and volumes
- CRITICAL: If the document has tier columns (Tier A/B/C etc.), create a SEPARATE entry for EACH tier where volume > 0 or status = "Yes"
- Example: "KV 360" with Tier A=No/0, Tier B=Yes/1, Tier C=Yes/1 → TWO entries: {name:"KV 360", tier:"Tier B", volume:1} and {name:"KV 360", tier:"Tier C", volume:1}
- Example: "KV 360" with Tier A=No/0, Tier B=Yes/1, Tier C=Yes/1 → TWO entries: (name="KV 360", tier="Tier B", volume=1) and (name="KV 360", tier="Tier C", volume=1)
- Do NOT create entries for tiers with volume=0 or status="No"
- Skip rows that are questions, metadata, or caveats — those are not deliverables
- Carry forward category names from merged cells (the analysis explains the hierarchy)