Skip to content

feat: Add retry button and book link to downloads page#68

Merged
boludo00 merged 1 commit intodevelopfrom
feature/retry-downloads
Mar 2, 2026
Merged

feat: Add retry button and book link to downloads page#68
boludo00 merged 1 commit intodevelopfrom
feature/retry-downloads

Conversation

@boludo00
Copy link
Copy Markdown
Owner

@boludo00 boludo00 commented Mar 2, 2026

Problem

When a download failed on the downloads page, there was no way to retry it inline — users had to navigate away, find the book again, and re-search/re-download. There was also no way to click through to the book's detail page from the downloads list.

Changes

Retry failed downloads inline

  • Error-state tasks now show an amber ↺ Retry button in the actions column
  • Clicking it deletes the error task and immediately re-queues the same download using the stored download_url, protocol, format, and book_id — no searching required
  • Loading state shown while the retry is in flight

Navigate to book from downloads list

  • The title cell now shows a "View Book" link (↗ ExternalLink icon) that navigates to /book/{book_id}
  • Replaces the unhelpful "Book ID: X" text

API type fix

  • Made indexer and size_bytes optional on downloadRelease — they're metadata fields not needed for the actual download, and aren't stored on the task record

Before / After

Before After
Error task — only delete button Error task — Retry button + delete button
"Book ID: 42" in title cell "↗ View Book" link to /book/42

- Failed downloads now show an amber Retry button in the actions column
  that re-queues the exact same download (deletes the error task first,
  then calls downloadRelease with the stored url/protocol/format)
- Title cell now shows a "View Book" link navigating to /book/{book_id}
  so users can reach the book detail page directly from download history
- Make indexer and size_bytes optional in downloadRelease API type
  to support retry without needing the full original release metadata
@boludo00 boludo00 merged commit 1e6c5ea into develop Mar 2, 2026
2 checks passed
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.

1 participant