refactor(actions): adopt endpoint client in portal service reads
This commit is contained in:
@@ -1544,3 +1544,31 @@ Validation:
|
||||
Follow-ups:
|
||||
|
||||
- Optional next bounded slice: adopt endpoint client helpers in selected `portalDirectService` GET/POST helper paths while preserving delete/hash flow semantics.
|
||||
|
||||
---
|
||||
|
||||
### CL-042: TASK22260 next slice — portal direct service partial endpointClient adoption
|
||||
|
||||
date: 2026-03-25
|
||||
author: Cline
|
||||
scope: `actions/services/portalDirectService.js`
|
||||
type: change
|
||||
rationale: Continue phased client-layer adoption by migrating low-risk portal direct-service read/create paths to shared endpoint request helpers while leaving hash-sensitive delete/message flows unchanged.
|
||||
impact: Reduces duplicated axios response extraction on high-traffic portal retrieval paths and keeps hashed delete/message semantics stable.
|
||||
status: completed
|
||||
|
||||
Summary:
|
||||
|
||||
- Refactored selected `portalDirectService` functions to use shared endpoint client helpers:
|
||||
- `getJson(...)` for read/listing routes (`getMyCases`, `getMyInvolvements`, `getMyLPACases`, representations, watched, awaiting submission variants)
|
||||
- `requestJson(...)` for `createWatchedCases`
|
||||
- Preserved existing hash/delete/message flow implementations (`deleteMyRepresentations`, `deleteWatchedCases`, completion message functions) using existing axios + relay signing behavior.
|
||||
- Preserved existing catch-path logging behavior for all migrated functions.
|
||||
|
||||
Validation:
|
||||
|
||||
- `npm run lint` -> warnings only (pre-existing `react-hooks/exhaustive-deps`; no new lint errors)
|
||||
|
||||
Follow-ups:
|
||||
|
||||
- Optional next bounded slice: migrate remaining non-hash POST helpers in `portalDirectService` (`setRepInvolvment`, `setCaseInvolvment`) to `requestJson` for full internal consistency.
|
||||
|
||||
Reference in New Issue
Block a user