Think about how different item kinds should be handled. #2

Closed
opened 2025-01-09 18:09:20 +01:00 by redxef · 1 comment
Owner

Currently items can be BaseItemKind.Audio, BaseItemKind.MusicAlbum and BaseItemKind.Playlist.

This is cumbersome, since nearly every smart playlist has to specifically exclude other playlists. Additionally more kinds of items would be nice.

I have two ideas how to proceed:

  1. Keep the implementation as is and just add more BaseItemKinds, maybe all
  2. A select multiple field like for users.
Currently items can be `BaseItemKind.Audio`, `BaseItemKind.MusicAlbum` and `BaseItemKind.Playlist`. This is cumbersome, since nearly every smart playlist has to specifically exclude other playlists. Additionally more kinds of items would be nice. I have two ideas how to proceed: 1. Keep the implementation as is and just add more BaseItemKinds, maybe all 2. A `select multiple` field like for users.
redxef added the
enhancement
label 2025-01-09 18:09:21 +01:00
redxef added reference enable-all-item-kinds 2025-01-16 18:56:42 +01:00
Author
Owner

Since the official recommendation is to always specify the kind in the filter I'm for now fine with option 1. Lets see how we fare with this. I can see performance becoming an issue though.

Since the official recommendation is to always specify the kind in the filter I'm for now fine with option 1. Lets see how we fare with this. I can see performance becoming an issue though.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: redxef/jellyfin-smart-playlist#2
No description provided.