Repository navigation
feat: remember browse categories and add clean URL routes - #23
Open
pushpinderbal wants to merge 1 commit into
Open
pushpinderbal wants to merge 1 commit into
pushpinderbal wants to merge 1 commit into
Conversation
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.
Returning to Movies, Shows, or Live TV previously reset the category to All, and URLs mixed page destinations with leftover browsing state. Each section now remembers its last category in localStorage for the current account, while explicit links remain authoritative.
React Router provides clean paths for libraries, Search, Settings, title details, and playback. Existing query-based bookmarks normalize to the new paths without adding a history entry. Navigation uses real links, and the Go server serves the app for known frontend routes so direct loads and refreshes work while missing assets and API routes retain their errors. Playback origin, scroll restoration, and Back/Forward behavior are preserved.
Validation:
go test ./...passed, including frontend deep-link GET/HEAD and missing-file coverage.