Skip to content

feat(configure): give Jellyfin and People their own settings tabs - #911

Merged
0xConstant1 merged 1 commit into
cedya77:tracker-dashboardfrom
0xConstant1:feat/jellyfin-settings-page
Nov 12, 2026
Merged

0xConstant1 merged 1 commit into
cedya77:tracker-dashboardfrom
0xConstant1:feat/jellyfin-settings-page

Conversation

@0xConstant1

Copy link
Copy Markdown
Collaborator

Summary

Moves the Jellyfin dialog into its own Jellyfin settings tab, laid out in the order you set Jellyfin up: server address, sign in, playback, browsing. Household members get their own People tab instead of a panel at the bottom of Watch Tracking. Every setting keeps its config key and default; only where it lives and how it is presented changes. No server changes.

Why this approach

  • One home per setting. A person's settings live on their card in People (Profile, Tracking, Catalogs, Jellyfin). Feature tabs hold only settings for everyone, and links between tabs point forward in nav order: Catalogs, People, Watch Tracking, Jellyfin.
  • Jellyfin tab. A status strip, the server address with copy, Quick Connect with a six-box code input (it asks who the app is for once several people exist, and can add a person inline), the client password with reveal and a confirm before replacing, the stream addon with a live manifest check, skip markers, and the browsing options.
  • Hidden when off. With JELLYFIN_API_ENABLED off the tab is left out of the nav, the mobile picker, prev/next and search, and #jellyfin falls back to General.
  • One read of /api/config. useJellyfinServer is a single React Query instead of several separate fetches.
  • Old links keep working. #watch-tracking/household-users.<id> redirects to #people/<id>.
  • The Configuration tab's Jellyfin button now opens the tab, and JellyfinDialog.tsx is removed.

@0xConstant1
0xConstant1 merged commit 6e6602c into cedya77:tracker-dashboard Nov 12, 2026
1 check passed
@0xConstant1
0xConstant1 deleted the feat/jellyfin-settings-page branch November 12, 2026 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant