ChicoryTV SPA: Guide / EPG screen #85
No Assignees
Notifications
Due Date
No due date set.
Blocks
Depends on
#91 ChicoryTV SPA: Blazor → SPA cutover (retire old UI)
timothy/ersatztv
#82 ChicoryTV SPA: app shell (sidebar + top bar + routing)
timothy/ersatztv
#102 Backend: JSON channel-guide endpoint for the EPG grid
timothy/ersatztv
Reference: timothy/ersatztv#85
Reference in New Issue
Block a user
Recreate
design-system/templates/chicorytv-admin/Epg.jsxwired to the channel guide data (XMLTV/guide handler).Dark channels×time grid, "now" marker, live focal color, jump-to-now. Acceptance: matches prototype; live guide data; all 3 themes.
Heads-up from #102 (JSON guide endpoint, PR incoming): (1)
fillerKindon programmes will almost always beNone— the shared XMLTV/JSON projector merges filler into adjacent programmes; discrete filler entries would need a JSON-only projection mode (open a follow-up if the grid needs it). (2) The endpoint eager-loads the full metadata graph per channel per request — do not poll it aggressively; a trimmed projection/caching follow-up is advised before this grid ships.Approach before coding
I’m implementing this as a frontend-only Guide screen in
web/, matchingdesign-system/templates/chicorytv-admin/Epg.jsxand the existing Channels/Schedules/Playouts/Libraries patterns.Prototype → API/client mapping:
num,name/api/guidechannels[].number,channels[].name; render with existingChannelLogoinitials precedent/api/guideprogrammes[].title,subTitle,category; null subtitle/category render as omitted/muted metadataprogrammes[].fillerKind; explicitly compare to'None'rather than truthiness-checkingDatemath, clip programmes to window before computing left/width/api/channels/statepoll at ≥30s foronAir/live channel treatment/api/guide?start=&end=window when neededScope decisions:
now - 1hthroughnow + 12h, aligned in client code and always sent explicitly as query parameters to avoid the expensive default horizon./api/guide; interval ticks only move the marker/highlight./api/channels/statemay poll at the Channels precedent cadence if used for live focal treatment.fillerKind: 'None'fixtures with null subtitle/category.Progress
Implemented the Guide/EPG screen in the isolated
feat/85-epgworktree:web/src/api/guide.tsfor bounded/api/guide?start=&end=loading plus optional/api/channels/statelive-state refresh./app/guideplaceholder with a channels × time grid, sticky channel rail/time header, programme clipping, empty-channel rows, now marker, previous/next window controls, and jump-to-now./api/guidefetches explicit and navigation-driven only; the now marker moves on a client-side timer without refetching guide data.fillerKind: 'None', and error+retry.Verification so far:
npm cipassednpm run typecheckpassednpm run lintpassednpm test -- --runpassed (79 tests)npm run buildpassedTZ=UTC dotnet build ErsatzTV.slnpassed with existing NuGet audit warnings and existing nullable warnings inArtworkUploadControllerTestsTZ=UTC dotnet test ErsatzTV.Tests/ErsatzTV.Tests.csprojpassed (368)TZ=UTC dotnet test ErsatzTV.Core.Tests/ErsatzTV.Core.Tests.csprojpassed (493 passed, 1 skipped)A read-only code review agent is running now before I push/open the PR.
Done
What was done: Implemented the Guide / EPG screen in PR #129 (
feat/85-epg, head7d93688841aa0115c2d603cf274153643f0f768e). The screen uses a bounded/api/guide?start=&end=window, renders the channels × time grid with clipped programme blocks, moves the now marker client-side without guide polling, uses/api/channels/statefor live styling, supports previous/next window and jump-to-now, and includes error/retry and empty-row states.Root cause: n/a — frontend feature implementation.
Files changed:
web/src/api/guide.ts,web/src/api/index.ts,web/src/App.tsx,web/src/App.test.tsx,web/src/shell.css.Verification:
npm ci;npm run typecheck;npm run lint;npm test -- --run(79 passed);npm run build;TZ=UTC dotnet build ErsatzTV.sln(passed with existing NuGet audit warnings);TZ=UTC dotnet test ErsatzTV.Tests/ErsatzTV.Tests.csproj(368 passed);TZ=UTC dotnet test ErsatzTV.Core.Tests/ErsatzTV.Core.Tests.csproj(493 passed, 1 skipped). A read-only review found three risks; all were addressed before push: same-window request sequencing, live matching by title+timestamps, and toolbar wrapping.Deferred: Discrete filler-entry display remains deferred until the backend exposes a JSON-only projection mode. Channel group filtering is visibly disabled until guide rows expose group data.
/api/guideremains expensive, so the screen intentionally avoids polling it.Follow-up issues: none opened in this session.
Docs updated: PR body documents the endpoint mapping, scope decisions, review fixes, and deferred items.
Status: PR #129 is open and pushed. Issue #85 should remain open until Fable review, CI, user merge consent, and merge. CI is currently pending/queued on Gitea run 247.
Done
What was done: Addressed Fable review comment 6382 on PR #129 and pushed commit
a8d4979b0ceeb5b236860479d22821831fe77d45. The omitted-nowPlayingcrash is fixed with a truthiness guard and a fixture that omits the key; live highlighting now matches by exact start/finish timestamps only; optional channel-state failure no longer takes down initial guide loading; shared guide window constants/helpers are reused; the jump-to-now duplicate lookback is removed; and the crosshair icon now uses lucide.Root cause: The frontend assumed
nowPlayingwould deserialize asnull, but the API omits null fields. The live-match logic also relied on title equality across two endpoints with different title contracts: guide programme titles are show-level, while now-playing titles are display titles.Files changed:
web/src/api/guide.ts,web/src/App.tsx,web/src/App.test.tsx,web/src/shell.css.Verification:
npm run typecheck;npm run lint;npm test -- --run(80 passed);npm run build. Earlier full PR verification also covered .NET build/tests. Gitea Actions run 512 is currently in progress for the new head SHA.Deferred: Shared poll-loop extraction and full-grid memoization remain non-blocking cleanups. Existing deferred scope remains: discrete filler rows need backend projection support; channel group filtering awaits group data in guide rows;
/api/guideis intentionally not polled.Follow-up issues: none opened; timestamp-only matching resolved the review's #2 without needing a backend ID follow-up for this PR.
Docs updated: PR #129 body updated with the corrected review-fix summary and current verification.
Status: PR #129 remains open. Issue #85 remains open until the new CI run is green, Fable/user consent is given, and the PR is merged.