Merge Frontend connections to auth page, improved first time setup #127
Merged
LumePart merged 6 commits intoLumePart:feat/backendfrom May 5, 2026
Merged
Merge Frontend connections to auth page, improved first time setup #127LumePart merged 6 commits intoLumePart:feat/backendfrom
LumePart merged 6 commits intoLumePart:feat/backendfrom
Conversation
…als to docker-compose template, added auth to GET /api/ui/config
…tched during wizard setup
LumePart
approved these changes
May 5, 2026
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
2 participants
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.
Meant to complete the frontend for #121
Hey! here's my page for the frontend connections for the auth page :) I moved the login screen out of the wizard and now have a proper Login.jsx page, alongside the ability to log out.
The app now starts by checking two things before loading the UI:
/api/ui/auth/status/api/ui/setup-statusand fetches config only after auth succeeds.
The setup status check reads the existing
WIZARD_COMPLETEflag, so the frontend can decide on the fly whether the user should go to the setup wizard or straight into the settings/home UI.I also added an playlist prefetch endpoint:
POST /api/ui/playlists/prefetchIn the wizard, once the user completes step 1, the frontend now calls the new playlist prefetch endpoint and starts caching their playlists and cover-art in the background. This is nice so by the time the user finishes the setup wizard, playlist cards already have cached tracks and cover art ready to render! And after the first time setup, the login/wizard screens will use the user’s own recommendation cover art so it feels really personalized.
If no local playlist/cover cache exists yet, the the background falls back to ListenBrainz global top albums so the UI still has a usable background.
The wizard also uses that same cached artwork as a blurred background, so setup feels visually connected to the rest of the app instead of being a plain form screen.
I also locked down any UI endpoints that should require an authenticated session before loading or mutating user config/data.
GET /api/ui/configGET /api/ui/config/rawPOST /api/ui/configPOST /api/ui/config/resetPOST /api/ui/config/schedulesPOST /api/ui/wizard/step1POST /api/ui/wizard/step2POST /api/ui/wizard/step3GET /api/ui/browsePOST /api/ui/runGET /api/ui/run/eventsPOST /api/ui/run/stopGET /api/ui/run/statusGET /api/ui/logsGET /api/ui/playlistsPOST /api/ui/playlists/prefetchPOST /api/ui/logoutHopefully this passes now, thanks again! Let me know if you have questions.