fix(api): include proceeding_type in /api/cases list response
All checks were successful
Build & Deploy / build-and-deploy (push) Successful in 9s

The cases-table reads from the list endpoint, not /details, so without
proceeding_type in the row payload the בל"מ badge can't render for
cases that flipped the field manually (only the legacy
appeal_subtype LIKE 'extension_request_%' path was firing).

Added the field to both detail=false and detail=true branches.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-26 10:01:24 +00:00
parent ac3ed455cf
commit d32452f95c

View File

@@ -1099,6 +1099,7 @@ async def list_cases(
"updated_at": c["updated_at"].isoformat() if c.get("updated_at") else None,
"practice_area": c.get("practice_area"),
"appeal_subtype": c.get("appeal_subtype"),
"proceeding_type": c.get("proceeding_type"),
}
for c in cases
]
@@ -1128,6 +1129,7 @@ async def list_cases(
"updated_at": c["updated_at"].isoformat() if c.get("updated_at") else None,
"practice_area": c.get("practice_area"),
"appeal_subtype": c.get("appeal_subtype"),
"proceeding_type": c.get("proceeding_type"),
"document_count": doc_count,
"processing_count": processing_count,
"gitea_url": f"https://gitea.nautilus.marcusgroup.org/cases/{c['case_number']}",