fix: handle playlists with slashes in their names #2534
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title
Fix: handle playlists with slashes in their names
Description
This PR fixes an issue where playlists containing slashes in their names would cause a FileNotFoundError when creating M3U files. The fix works by:
Related Issue
Fixes #2284
Motivation and Context
When a playlist name contained slashes like "init 3 - Neutral/Happy", the sanitize_string function would remove the slashes completely, resulting in filenames like "init 3 - NeutralHappy.m3u8". Additionally, if the directory structure didn't exist, the program would crash with a FileNotFoundError when trying to create the M3U file.
How Has This Been Tested?
Tested on Windows with playlist names containing slashes. The changes ensure that:
Screenshots (if appropriate)
Types of Changes
Checklist