Skip to content

feat(core): page between jobs from the detail view#43

Open
omar-zeineddine wants to merge 1 commit into
pontusab:mainfrom
omar-zeineddine:feat/job-prev-next-nav
Open

feat(core): page between jobs from the detail view#43
omar-zeineddine wants to merge 1 commit into
pontusab:mainfrom
omar-zeineddine:feat/job-prev-next-nav

Conversation

@omar-zeineddine

Copy link
Copy Markdown

Problem

The job detail page had no way to move to an adjacent job — to see the next one you had to go back to the queue list and click into it. Stepping through a run of jobs (e.g. reviewing a batch of failures) meant a lot of back-and-forth.

Fix

Add prev/next navigation to the job detail view:

  • Chevron buttons to the left of the job title, plus ← / → arrow-key shortcuts (ignored while typing in an input/textarea/contenteditable).
  • Paging follows the same list, status filter, and sort the queue page was showing. The queue's status/sort now ride along in the URL (added to jobSearchSchema) and are passed when opening a job, so prev/next on a Failed-filtered, custom-sorted view stays within that view. Deep links, the command palette, and the Runs page (which carry no list context) fall back to the full job list for that queue.
  • Reuses the shared useJobs query — same cache key as the queue list — so navigation is instant when coming from the list, and it auto-fetches the next page when you reach the last loaded job so "next" doesn't dead-end mid-queue.
  • Buttons disable at the ends of the list (and when the current job isn't in the loaded set, e.g. a deep link far down the queue), so there's no runaway pagination.

Testing

  • tsc --noEmit
  • biome check
  • vite build (UI bundle) ✅

@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown

@omar-zeineddine is attempting to deploy a commit to the Pontus Abrahamsson's projects Team on Vercel.

A member of the Team first needs to authorize it.

@omar-zeineddine omar-zeineddine force-pushed the feat/job-prev-next-nav branch from 380f2a5 to 3e18f25 Compare June 24, 2026 17:38
Previously the only way to move between jobs was back to the queue
list and into the next one. Add prev/next navigation to the job detail
page so you can step through a queue in place:

- Chevron buttons (left of the title) plus arrow-key shortcuts
  (left/right), ignored while typing in inputs.
- Paging follows the same list, status filter, and sort the queue
  page was showing — the queue's status/sort ride along in the URL
  (added to jobSearchSchema), so prev/next on a Failed-filtered view
  stays within failed jobs. Deep links / command palette / Runs fall
  back to the full queue list for that queue.
- Reuses the shared useJobs query (same cache key as the list) so
  navigation is instant, and auto-fetches the next page when you reach
  the last loaded job so next doesn't dead-end. Buttons disable at the
  ends of the list.
@omar-zeineddine omar-zeineddine force-pushed the feat/job-prev-next-nav branch from 3e18f25 to 1b7f1fa Compare June 24, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants