android: Now Playing shows no composer for a lone classical track without a work tag
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start with Song.classicalText() and nowPlayingWork() in android/domain/.../model/ClassicalDisplay.kt, then compare their behavior for a track with no WORK tag to the album page heading. Use the test-media/classical/recital-montesinos fixture to check the lone-track case. Done means Now Playing shows the composer for a lone classical track without a WORK tag.
Written by the indexing model from the issue text.
Description
On a recital album, a lone classical track with no WORK tag (e.g. Tárrega's "Capricho Arabe" or Mertz's "Hungarian Fantasy" on Erik's Guitar Recital album) plays with Now Playing reading "Title / Anabel Montesinos • Guitar Recital [TEST]": the composer appears nowhere, although the file carries COMPOSER and the album page now shows it as a heading (#1080).
Song.classicalText() (android/domain/.../model/ClassicalDisplay.kt) only builds the work line from workLine(), which is null without a work, so the subtitle falls back to artist • album. nowPlayingWork() likewise only produces a composer eyebrow for runs of 2+ movements.
Expected: a lone classical track shows its composer somewhere on Now Playing (the eyebrow, or "Composer • Performer" in the subtitle), consistent with the album page heading.
Seen on the emulator (lane 1, pool-6 build of main + the #1081/#1082 branches) with the recital fixture in test-media/classical/recital-montesinos.
Impact U2 (classical listener loses the primary identity of the piece on the player) · Reach R1 (lone tracks without a WORK tag; one user's library) · Implemented: no · Design fit: fits (#1065 wants the composer on Now Playing) · Complexity: S
- Dominant language
- Kotlin
- Stars
- 231
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from timusus/Shuttle2
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
idea
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
later
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
later
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
later next-release
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in timusus/Shuttle2
Similar issues
-
area:ide bug platform:intellij
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anthropics/claude-code#104508 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
lugassawan/swe-workbench#823 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
Droid-Deck/DroidDeck#1355 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
IronCoreLabs/ironcore-alloy#351 ·