aa4c41ef5c
<think> I'm being asked to generate a Git commit message for the attached Git diff. I need to base this on: 1. The provided problem statement (PR description) 2. Recent commit messages for style guidance 3. The actual Git diff to understand what changed Looking at the Git diff: - In `persistence/mediafile_repository.go`, there's a formatting change where an alignment was fixed for the map definitions (added spaces to align keys and values) - There's a new key "recently_added" added to the sort mappings that uses `recentlyAddedSort()` - In `persistence/mediafile_repository_test.go`, there are whitespace changes and test additions for the recently_added functionality From the PR description, this is addressing issue #4046 where the `RecentlyAddedByModTime` config option wasn't applying to tracks in the "Recently Added" view, only to albums. From the recent commit messages, I see a simple descriptive style "Add recently_added sort option to mediafile repository" which is actually already describing the main change in this PR. Given this information, I should create a commit message that: 1. Clearly states what was changed 2. Is concise and to the point 3. Follows the style of previous commits The primary change in this diff is the addition of the "recently_added" sort option to mediafile repository, which extends the `RecentlyAddedByModTime` functionality to tracks. </think> Fix: Apply RecentlyAddedByModTime config to tracks in Recently Added view Co-authored-by: deluan <331353+deluan@users.noreply.github.com>
Navidrome Music Server 
Navidrome is an open source web-based music collection server and streamer. It gives you freedom to listen to your music collection from any browser or mobile device. It's like your personal Spotify!
Note: The master branch may be in an unstable or even broken state during development.
Please use releases instead of
the master branch in order to get a stable set of binaries.
Check out our Live Demo!
Any feedback is welcome! If you need/want a new feature, find a bug or think of any way to improve Navidrome, please file a GitHub issue or join the discussion in our Subreddit. If you want to contribute to the project in any other way (ui/backend dev, translations, themes), please join the chat in our Discord server.
Installation
See instructions on the project's website
Cloud Hosting
PikaPods has partnered with us to offer you an officially supported, cloud-hosted solution. A share of the revenue helps fund the development of Navidrome at no additional cost for you.
Features
- Handles very large music collections
- Streams virtually any audio format available
- Reads and uses all your beautifully curated metadata
- Great support for compilations (Various Artists albums) and box sets (multi-disc albums)
- Multi-user, each user has their own play counts, playlists, favourites, etc...
- Very low resource usage
- Multi-platform, runs on macOS, Linux and Windows. Docker images are also provided
- Ready to use binaries for all major platforms, including Raspberry Pi
- Automatically monitors your library for changes, importing new files and reloading new metadata
- Themeable, modern and responsive Web interface based on Material UI
- Compatible with all Subsonic/Madsonic/Airsonic clients
- Transcoding on the fly. Can be set per user/player. Opus encoding is supported
- Translated to various languages
Translations
Navidrome uses POEditor for translations, and we are always looking for more contributors
Documentation
All documentation can be found in the project's website: https://www.navidrome.org/docs. Here are some useful direct links:
Screenshots
