libretro / libretro/RetroArch

[Feature Request] Option to prepend favourites at top of console playlists

Open
#18,453 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Hey everyone :-)

I would like an toggle option in the playlist settings that would enable/disable prepend all favourites from a console playlist to the top of the same console playlist. For example:

After scanning a directory of roms a Nintendo Entertainment System console playlist is automatically created, and when I navigate into that playlist and favourite Blaster Master, if the aforementioned option is enabled, then Blaster Master will automatically appear at the top of the Nintendo Entertainment System, as well as in the Favourites playlist.

The reasons I would like this feature:

  • It could eliminate the need for micro managing lpl files needed to have more granular playlists.
  • It could eliminate the need for using additional frontends to simplify file navigation; I only use ES-DE because finding favourites is easier by sorting to the top.
  • Makes console playlists which have been populated with very large numbers of roms (100s or 1000s) more usable, instead of being impractical except for adding additional roms to the favourites playlist.

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating RetroArch's playlist settings and the code that handles favourites within console playlists. Define how the toggle should affect ordering in the existing playlist while preserving the Favourites playlist, then identify suitable tests or manual verification for large playlists.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.