Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

downloads: SongDownloadRepository/Manager methods unused until a status UI lands

Open Beginner friendly
  • Is something wrong?
#320 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
kotlin
Domain
mobile

Research direction

Review the offline downloads engine commits (8bd6a5c2, 656b7c64) and locate SongDownloadRepository.kt and SongDownloadManager.kt. Examine the unused methods: observeDownload(path), observeDownloadedPaths(), getDownload(path), and removeAll(). Determine if a downloads-status UI is being developed that will use them, or if they should be removed. Check related issue #88 for context. Run existing tests to ensure no regressions.

Written by the indexing model from the issue text.

Description

task

The offline downloads engine (8bd6a5c2, wired in 656b7c64) exposes repository/manager methods with no callers yet in app code:

  • SongDownloadRepository.observeDownload(path) (SongDownloadRepository.kt:28)
  • SongDownloadRepository.observeDownloadedPaths() (SongDownloadRepository.kt:31)
  • SongDownloadRepository.getDownload(path) (SongDownloadRepository.kt:33)
  • SongDownloadManager.removeAll() (SongDownloadManager.kt:25)

Found while reviewing #88 (rebase + migration renumber + main-thread fix). Left in place rather than deleted since they read as intentional API for a future downloads-status UI slice (mirrors the used observeDownloads()/manager download API), not leftover refactor cruft — but flagging so whoever picks up the next slice either wires them up or trims them if the design changes.

Dominant language
Kotlin
Stars
228
Forks
25
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from timusus/Shuttle2

All issues in timusus/Shuttle2

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.