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

This commit is contained in:
2026-03-25 06:43:51 +00:00
parent 6e6a104dd9
commit 17be69323e
2 changed files with 82 additions and 69 deletions
+34
View File
@@ -1600,3 +1600,37 @@ Validation:
Follow-ups:
- Optional next bounded slice: begin selective `requestJson` adoption for remaining config-based calls in `documentDirectService` where hash flow is already centralized.
---
### CL-044: TASK22260 next slice — document direct service low-risk getJson adoption
date: 2026-03-25
author: Cline
scope: `actions/services/documentDirectService.js`
type: change
rationale: Continue incremental façade/client rollout by migrating low-risk document service GET wrappers that already return JSON and do not alter hash-signing semantics.
impact: Reduces duplicated axios `.get(...).then(res => res.data)` boilerplate and aligns document retrieval helpers with shared endpoint client usage.
status: completed
Summary:
- Added `getJson` usage in selected document service helpers:
- `getRepsFromBlobProxy`
- `getAwaitingSubmissionFromBlobProxy`
- `getFilesFromBlobproxy`
- `getFilesFromBlobHashed`
- `getProgressFromBlob`
- `createContainerProxy`
- Preserved existing behavior contracts:
- same query composition and hash query fragments
- same catch-path logging and return conventions (including JSON string return in `createContainerProxy` error path)
- Left hash-sensitive delete/upload/generation flows unchanged in this slice.
Validation:
- `npm run lint` -> warnings only (pre-existing `react-hooks/exhaustive-deps`; no new lint errors)
Follow-ups:
- Optional next bounded slice: migrate selected `requestJson`-eligible upload/generation helpers in `documentDirectService` (non-download paths) while preserving multipart/blob behavior.