Person ItemView

[JPKribs]

Summary

Resolves: #1590
Resolves: #1551 (Subject to change)

Creates an ItemView for people and artists. This can be used instead of the existing process where selecting a person goes to a PagingLibraryView with content from that person.

iPadOS

Videos

From Search

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-06-22.at.19.44.51.mp4

---

From Cast & Crew

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-06-22.at.19.45.37.mp4

[JPKribs]

@LePips How would you prefer I handle this? All in 1 PR for iOS and tvOS or just iOS first then tvOS separate?

At this point, iOS & iPadOS should be ready to go. I'm leaving this as WIP in case we want to add tvOS as well in this PR.

[LePips]

Just do iOS for now. There should also be cleanup in PagingLibraryView.

[LePips]

I've abstracted out the item type library fetching, which can also eventually use used for Media/Favorites. I've also accounted for some other interactions and brought over some work from my poster button cleanup.

There was one bug where the Collections would say it contained every Collection item?

On the server if the requested item type only has a single element and is the boxset type, it nullifies the parent ID. I'm unsure why this is the case, but it wouldn't hurt to investigate if the web or other clients use this behavior and get rid of this behavior, or have us find a workaround.

https://github.com/jellyfin/jellyfin/blob/630846798d8302ea5ed805ade669158b7af2f123/Jellyfin.Api/Controllers/ItemsController.cs#L274

[JPKribs]

it wouldn't hurt to investigate if the web or other clients use this behavior and get rid of this behavior, or have us find a workaround.

It looks like Jellyfin-Web just groups multiple items together so the call would have more than one ItemType filter in it:

https://github.com/jellyfin/jellyfin-web/blob/master/src/controllers/itemDetails/index.js#L1694C1-L1700C10

Testing, this is what this looks like: