Feat/rename catalog

[TimilsinaBimal]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
watchly	Ready	Preview	Comment	Dec 6, 2025 5:18pm

[gemini-code-assist]

Summary of Changes

Hello @TimilsinaBimal, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a major overhaul to the application's user authentication and dynamic catalog features. By transitioning to a Stremio-auth-key-only login, it significantly simplifies the user experience and backend logic for managing user identities. The changes also enhance the recommendation system by providing more distinct and configurable 'loved' and 'watched' catalogs, all presented through a refreshed and more interactive user interface.

Highlights

• Authentication & User Management Simplification: The system now exclusively uses Stremio's authentication key for user login and identity verification, removing the previous Watchly-specific username/password system. This streamlines the login process and enhances security by centralizing identity with Stremio.
• Catalog Granularity: The 'Because you Loved/Watched' catalog has been split into two distinct categories: 'More like what you loved' (watchly.loved) and 'Because you watched' (watchly.watched), offering more precise recommendations and user control. All catalog items are now renamable in the UI.
• Frontend UI/UX Enhancements: The welcome page has been redesigned with a modern layout and feature highlights. A user profile display is now integrated into the sidebar, and new interactive elements like toast notifications and a custom confirmation modal have been added for improved user feedback. Manual credential input fields have been removed, simplifying the Stremio login flow.
• Backend Refactoring: The token storage mechanism has been updated to directly use the Stremio user ID, eliminating complex token derivation and encryption. Catalog generation logic has been refined to support the new granular catalog types and improve year-based discovery queries.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a major and beneficial refactoring of the authentication and user management system. It moves away from a custom credential system to one that is tightly integrated with Stremio's authentication, using the Stremio user_id as the primary identifier. This simplifies the user flow, improves security by not storing Stremio credentials, and streamlines the codebase. The frontend has been significantly updated to reflect this new, simpler user experience. My review includes suggestions to improve code clarity, remove dead code, and address a potential runtime error in the JavaScript.

I am having trouble creating individual review comments. Click here to see my feedback.

app/static/script.js (682-687)

This else if block for stremioAuthSection appears to be dead code. The element stremioManualFields and its corresponding logic have been removed in this pull request. Calling document.getElementById('stremioManualFields') will return null, and attempting to access .classList will cause a TypeError.

Since this entire block is now obsolete, it should be removed to prevent potential runtime errors and to clean up the code.

    } else {

app/api/endpoints/catalogs.py (79)

The chained replace() calls to extract the item_id are a bit fragile and can be made more robust and elegant. A better approach would be to split the string to isolate the ID part, which is less prone to errors if the prefix format changes or if prefixes could theoretically appear in the item ID.

            item_id = id.split(".", 2)[-1]

app/api/endpoints/tokens.py (212-221)

This block of code to fetch the Stremio user ID from an auth key is duplicated in create_token, check_stremio_identity, and here in delete_token. To improve maintainability and reduce redundancy, consider extracting this logic into a shared private helper function or a FastAPI dependency.

app/core/constants.py (1)

This new constant RECOMMENDATIONS_CATALOG_NAME is a good addition for maintainability. However, it doesn't appear to be used anywhere in the project. It should be imported and used in app/api/endpoints/manifest.py to replace the hardcoded string "Top Picks for You".

app/services/token_store.py (60-73)

The new methods _encrypt_password and _decrypt_password seem to be unused following the refactoring, as passwords are no longer stored. If they are indeed obsolete, they should be removed to keep the codebase clean.