refactor(actions): adopt endpoint client in case service reads

This commit is contained in:
2026-03-25 07:36:53 +00:00
parent f4471c5702
commit c1f6cc9832
2 changed files with 51 additions and 32 deletions
+31
View File
@@ -1700,3 +1700,34 @@ Validation:
Follow-ups:
- Optional next bounded slice: targeted hygiene in `documentDirectService` to isolate remaining non-migrated special-case flows (`downloadBlob`, delete helpers) and assess if any shared client abstraction is beneficial without altering behavior.
---
### CL-047: TASK22260 next slice — case direct service low-risk getJson adoption
date: 2026-03-25
author: Cline
scope: `actions/services/caseDirectService.js`
type: change
rationale: Continue incremental endpoint client rollout with a bounded low-risk set of case service GET helpers that already return direct JSON payloads and have simple logging-only catch paths.
impact: Reduces repeated axios GET/response extraction boilerplate and aligns additional case retrieval helpers with shared client conventions.
status: completed
Summary:
- Added `getJson` usage in selected `caseDirectService` helper functions:
- `getAppealPDFDocs`
- `getPortalModuleDetails`
- `getPortalModuleDetailsProxy`
- Preserved existing behavior contracts:
- same request URL/query construction
- same catch-path logging via `consoleLogger`
- no change to handlers with bespoke error-return contracts (`getAppealPDFDocument`) or other non-targeted flows.
Validation:
- `npm run lint` -> warnings only (pre-existing `react-hooks/exhaustive-deps`; no new lint errors)
Follow-ups:
- Optional next bounded slice: migrate additional safe case service GET helpers that currently use `axios.get(...).then(res.data)` to `getJson` where custom catch behavior is compatible.