fix(jellyfin): use Search/Hints endpoint for playlist lookup#93
Merged
LumePart merged 1 commit intoLumePart:devfrom Jan 17, 2026
Merged
Conversation
Owner
|
Thanks for the PR! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I was trying to use a non-persistent weekly playlist with a Jellyfin client, with the persist flag set to false and USE_SUBDIRECTORY set to true as documented. This currently seems to be broken because of how the playlist is looked up before deletion in the Jellyfin client SearchPlaylist function.
SearchPlaylist was querying /Items but parsing the response as SearchHints, which caused playlist lookup to fail even when the playlist exists.
This switches the request to /Search/Hints with IncludeItemTypes=Playlist so the response matches the existing parsing logic.
I’m not very familiar with the Jellyfin API, so please let me know if there’s a better approach that preserves the current SearchPlaylist implementation.
Edit:
Current Jellyfin playlist search api call:
curl -H "X-Emby-Token: <jellyfin_api_token>" "http://<jellyfin_url>/Items?mediaTypes=Playlist&searchTerm=Weekly-Exploration&recursive=true"
Fixed Jellyfin playlist search api call:
curl -H "X-Emby-Token: <jellyfin_api_token>" "http://<jellyfin_url>/Search/Hints?IncludeItemTypes=Playlist&SearchTerm=Weekly-Exploration"