mirror of
https://github.com/navidrome/navidrome.git
synced 2025-07-17 08:52:01 +03:00
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>