Added match_existing_path_case option (#335)

When enabled, existing path components are reused even if Tidal returns
different casing. This avoids creating separate paths on case-sensitive
filesystems that would conflict later when moved to case-insensitive systems.
For example, if "FooBar" already exists and the API returns "foobar",
downloads will continue under "FooBar".

Co-authored-by: Piotr Karbowski <git.throwaway941@simplelogin.com>
This commit is contained in:
Piotr Karbowski
2026-04-25 00:55:02 +02:00
committed by GitHub
parent 658e4a81ab
commit b1e28a8ae6
7 changed files with 115 additions and 4 deletions
+7
View File
@@ -84,6 +84,13 @@ rewrite_metadata = false
# track file with the same name
write_lrc_file = false
# when enabled, existing path components are reused even if Tidal returns
# different casing. This avoids creating separate paths on case-sensitive
# filesystems that would conflict later when moved to case-insensitive systems.
# For example, if "FooBar" already exists and the API returns "foobar",
# downloads will continue under "FooBar".
match_existing_path_case = false
[metadata]
# embed metadata in files