TASK22269: reuse contentLength locals in touched azurestorage blob loops

This commit is contained in:
2026-03-26 11:36:47 +00:00
parent 48878e9ebd
commit 830e36d0c4
2 changed files with 39 additions and 4 deletions
+32
View File
@@ -3162,3 +3162,35 @@ Validation:
Follow-ups:
- Optional next bounded slice: continue tiny helper reuse in touched functions only if any duplicated path literals remain and can be reduced without behavior change.
---
### CL-089: TASK22269 Slice B1.14 — azurestorage touched-function contentLength local reuse
date: 2026-03-26
author: Cline
scope: `actions/azurestorage.js`
type: change
rationale: Execute the next tiny bounded readability slice by reusing local `contentLength` values in touched helper-consumer functions to reduce repeated property access and keep object assembly consistent.
impact: Maintainability/readability improvement only; no route/query/output behavior changes.
status: completed
Summary:
- In touched functions:
- `getBlobs`
- `getProgressBlobs`
- `getRepsFilesBlobs`
- Added local `contentLength` variable (`blob.properties.contentLength`) per loop iteration.
- Replaced repeated inline `blob.properties.contentLength` assignments in object assembly with the local variable.
- Preserved field contracts (`contentLength`, `size`) and values.
Validation:
- `npm run lint` -> pass with warnings only (pre-existing `react-hooks/exhaustive-deps`; no new lint errors)
- `node tests/phase22/index.test.cjs` -> pass
- `node tests/phase7/service-behaviour.test.cjs` -> pass (13/13)
Follow-ups:
- Optional next bounded slice: stop or switch scope; touched-function micro-tidies in this area are now largely exhausted.