diff --git a/Auto Run Docs/Initiation/2026-03-31-WebSocket-Progress-And-Polish/WEBSOCKET-PROGRESS-01.md b/Auto Run Docs/Initiation/2026-03-31-WebSocket-Progress-And-Polish/WEBSOCKET-PROGRESS-01.md index f711ad6..d9710cc 100644 --- a/Auto Run Docs/Initiation/2026-03-31-WebSocket-Progress-And-Polish/WEBSOCKET-PROGRESS-01.md +++ b/Auto Run Docs/Initiation/2026-03-31-WebSocket-Progress-And-Polish/WEBSOCKET-PROGRESS-01.md @@ -11,12 +11,13 @@ The backend event bus, WebSocket route, progress parser, and frontend context/ho - Ensure the provider is inside the existing `QueryClientProvider` (check `main.tsx` for provider ordering) - **Note:** Already wired in `main.tsx` (lines 25-29) from commit 0541a5f. Provider wraps entire app inside QueryClientProvider. No changes needed. -- [ ] Integrate DownloadProgressBar into the Queue page for actively downloading items: +- [x] Integrate DownloadProgressBar into the Queue page for actively downloading items: - Read `src/frontend/src/pages/Queue.tsx` and `src/frontend/src/components/DownloadProgressBar.tsx` - Search the existing codebase for how `useDownloadProgress` is intended to be used - In Queue.tsx, import `useDownloadProgress` from the DownloadProgressContext and `DownloadProgressBar` component - Create a small wrapper component (e.g., `QueueItemProgress`) that calls `useDownloadProgress(contentItemId)` and renders `` when progress exists, or falls back to the existing `` when no active progress - Update the `status` column render in the Queue table to use this wrapper for items with status `downloading` + - **Note:** Already wired from prior commits. `QueueItemProgress` component (lines 36-44) uses `useDownloadProgress(item.contentItemId)` and renders `` for active downloads, falling back to ``. Status column at line 94 uses this wrapper. Frontend builds clean, all 606 tests pass. - [ ] Integrate download progress into the Channel Detail page: - Read `src/frontend/src/pages/ChannelDetail.tsx` to understand how content items are displayed