Queue: history, undo remove, play-next grouping
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by locating the queue screen and its playback and swipe-to-remove entry points. Read how the current queue is rendered and updated, then check for existing UI tests. Done means previously played items appear above the current item, swipe removal can be undone, and “play next” insertions are visually grouped.
Written by the indexing model from the issue text.
Description
Show previously played items above the current one, offer undo after swipe-to-remove, and group "play next" insertions visually.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 30m
- Merged PRs (30d)
- 62
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 isaacault/polyphony
-
area/library area/ui priority/p1 type/feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
isaacault/polyphony#145 · 1 comment ·
Maintainers usually reply within 1 day
-
area/playback area/ui priority/p2 type/feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
area/cast priority/p2 type/verification
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
area/playback priority/p2 type/feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
area/transcoding priority/p2 type/feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
All issues in isaacault/polyphony
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mcnaveen/health-connect-webhook#110 ·
Maintainers usually reply within 1 day
-
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