mirror of
https://github.com/misiektoja/spotify_profile_monitor.git
synced 2026-04-25 23:15:57 +03:00
[PR #35] [MERGED] Add --export-all-playlists feature #36
Labels
No labels
Stale
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify_profile_monitor#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/misiektoja/spotify_profile_monitor/pull/35
Author: @tomballgithub
Created: 2/14/2026
Status: ✅ Merged
Merged: 2/15/2026
Merged by: @misiektoja
Base:
dev← Head:export_all📝 Commits (10+)
dfe62f8Add --export-all-playlists feature569cb42Cleanup & simplify down to original function "spotify_print_public_playlists"b8351a9Restore missing import72bc4f0Handle extension differently0c176b9don't export a playlist that is 'IGNORED'26041f9chore: handle pathvalidate dependency check47edf2bfeat: gate --export-all-playlists to -i modebe68b26docs(readme): add usage of --export-all-playlists flag05ce732chore: clarify help message for --export-all-playlists flag to indicate usage with --idee6acfchore: clarify help message for --export-all-playlists flag to indicate usage with -i📊 Changes
2 files changed (+44 additions, -11 deletions)
View changed files
📝
README.md(+6 -0)📝
spotify_profile_monitor.py(+38 -11)📄 Description
When using the -i feature (user_profile_details), adding --export-all-playlists will additionally export each of the user's playlist into a .CSV file named after the playlist.
I used this to sanitize the filenames:
from pathvalidate import sanitize_filenameThere doesn't seem to be another modern option. I looked elsewhere because I didn't like that it allows "!" in the filename.
But I figured it was good enough.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.