batch uploads on frontend

2026-04-02 16:09:56 +01:00
parent da7e694120
commit c754e04034
4 changed files with 212 additions and 21 deletions
@@ -3194,3 +3194,122 @@ Validation:
 Follow-ups:

 - Optional next bounded slice: stop or switch scope; touched-function micro-tidies in this area are now largely exhausted.
+
+---
+
+### CL-090: uploadsinglefile API batch upload chunking (10 files per pass)
+
+date: 2026-04-02
+author: Cline
+scope: `pages/api/file/uploadsinglefile.js`
+type: change
+rationale: Prevent oversized single-pass uploads by splitting validated files into bounded batches and invoking existing upload logic per batch.
+impact: Upload flow now processes validated files in deterministic chunks of 10 while preserving existing hash guards, validation behavior, and response contract (`data`, `invalidFiles`).
+status: completed
+
+Summary:
+
+- Added `MAX_FILES_PER_UPLOAD_BATCH = 10` in `uploadsinglefile` API route.
+- Replaced single `uploadSingleFile(...)` invocation with chunked processing:
+    - converts allowed files object to entries
+    - slices into batches of 10
+    - awaits `uploadSingleFile(...)` once per batch
+    - aggregates batch results into one `data` array for response
+- Kept existing error handling unchanged (`UPLOAD_SINGLE_FILE_FAILED` on catch).
+
+Validation:
+
+- `npx eslint pages/api/file/uploadsinglefile.js` -> executed with no lint output.
+
+Follow-ups:
+
+- Optional: add a focused API contract/unit test to assert that 11+ files cause multiple `uploadSingleFile` invocations with max chunk size 10.
+
+---
+
+### CL-091: uploadsinglefile client-side batch upload chunking parity (10 files per pass)
+
+date: 2026-04-02
+author: Cline
+scope: `actions/services/documentDirectService.js`
+type: change
+rationale: Ensure client upload flow aligns with server batching requirement by splitting outbound `uploadsinglefile` requests into chunks of 10 files.
+impact: Client now sends multiple sequential API requests (max 10 files each) and merges per-chunk responses into one contract-compatible payload (`data`, `invalidFiles`) for existing UI handlers.
+status: completed
+
+Summary:
+
+- Added `MAX_FILES_PER_UPLOAD_BATCH = 10` to document direct service.
+- Updated `uploadSingleFile(filesObj, containerID, casefolderID)` to:
+    - split selected files into batches of 10
+    - create a fresh `FormData` per batch
+    - call `/api/file/uploadsinglefile` once per batch (sequential `await`)
+    - aggregate `data` and `invalidFiles` from all chunk responses
+- Preserved function return shape used by current upload UIs.
+
+Validation:
+
+- `npx eslint pages/api/file/uploadsinglefile.js actions/services/documentDirectService.js` -> executed with no lint output.
+
+Follow-ups:
+
+- Optional: add a focused service-behaviour test that verifies `uploadSingleFile` issues N requests for N/10 chunks and merges all chunk responses.
+
+---
+
+### CL-092: per-chunk upload UI progress updates (new appeal + representations)
+
+date: 2026-04-02
+author: Cline
+scope: `actions/services/documentDirectService.js`, `components/elements/index.js`, `components/case/representation/representationElements.js`
+type: change
+rationale: Update UX so upload progress reflects completed chunks incrementally instead of waiting for all chunk requests to finish.
+impact: Upload status message now updates after each chunk completes, showing users progressive completion for large multi-file uploads while preserving existing response/error contracts.
+status: completed
+
+Summary:
+
+- Extended `uploadSingleFile(...)` service signature with optional callback support:
+    - new `options` argument
+    - invokes `options.onChunkComplete(...)` after each chunk upload
+    - emits cumulative counters (`cumulativeUploaded`, `cumulativeInvalid`, `processedFiles`, chunk index metadata)
+- Wired per-chunk UI progress updates in both upload entry points:
+    - `components/elements/index.js`
+    - `components/case/representation/representationElements.js`
+- Both now pass `onChunkComplete` and update `uploadCountMessage` from cumulative uploaded count as each chunk finishes.
+
+Validation:
+
+- `npx eslint pages/api/file/uploadsinglefile.js actions/services/documentDirectService.js components/elements/index.js components/case/representation/representationElements.js` -> executed with no lint output.
+
+Follow-ups:
+
+- Optional: add a focused UI behaviour test to assert upload progress increments per completed chunk for >10 file uploads.
+
+---
+
+### CL-093: upload progress message format `X of Y` during chunked uploads
+
+date: 2026-04-02
+author: Cline
+scope: `components/elements/index.js`, `components/case/representation/representationElements.js`
+type: change
+rationale: User requested clearer in-progress feedback showing uploaded count relative to total files (e.g. `10 of 30`) during chunked uploads.
+impact: Upload UI now shows progressive message in `X of Y` format while upload is in flight, improving clarity for large batch uploads.
+status: completed
+
+Summary:
+
+- Added `totalUploadFiles` state in both upload UIs (new appeal + representations).
+- In-progress upload message now renders as:
+    - `${uploadCountMessage} of ${totalUploadFiles}`
+- Upload start now initializes as `0 of Y` and updates after each completed chunk callback.
+- Empty-drop/reset path clears both counters to avoid stale totals.
+
+Validation:
+
+- `npx eslint actions/services/documentDirectService.js components/elements/index.js components/case/representation/representationElements.js` -> executed with no lint output.
+
+Follow-ups:
+
+- Optional: localize a dedicated `upload-progress-x-of-y` translation key if copy needs stronger grammatical control per locale.