[BW-DL-03] Correct download row actions: Pause, Resume and Retry #18
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Classification
Active follow-up from #15 / GitHub PR #106.
Problem / opportunity
The current Downloads row shows a Pause icon for every incomplete row that is not
Paused. That includesDownloadState.Failed. Pressing it callsPauseDownloadUseCase, which can turn a failed manifest intoPausedand clear its stored failure reason instead of retrying.User value
The action beside a download should always match what will happen: pause something that is actually transferring, resume something the listener paused, and retry something that failed.
Scope
Explicitly out of scope
Dependencies
Architecture seams affected
DownloadsViewModelaction routing.DownloadsScreenrow semantics/content descriptions.PauseDownloadUseCaseandDownloadBookUseCasecalls.Server / API assumptions
No new API. Retry/resume continues through
DownloadBookUseCase, which rechecks current profile download permission, asset metadata and allocatable storage before enqueueing.Storage / migration implications
None. Retry must preserve
.partdata and committed files. Pausing remains a durable manifest state as today.Privacy / security
No change to profile visibility. A hidden/title-redacted device-storage row may expose a generic recovery action/state but must not reveal media identity through error copy.
Automated-test level
PauseDownloadUseCase.DownloadBookUseCase, so authorization/free-space checks still run.Device / platform acceptance
Estimated effort
Small.
Implementation risk
Low to Medium. It changes user-triggered state transitions and must not make destructive restart behavior the default.
Recommended sequence
After #17, before BW-DL-04.
Acceptance criteria
Links