Skip to content

Conversation

@TimilsinaBimal
Copy link
Owner

No description provided.

@vercel
Copy link

vercel bot commented Dec 10, 2025

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

Project Deployment Preview Comments Updated (UTC)
watchly Ready Ready Preview Comment Dec 10, 2025 8:10am

@gemini-code-assist
Copy link

Summary of Changes

Hello @TimilsinaBimal, I'm Gemini Code Assist1! 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 significantly enhances the user experience by integrating the Gemini AI service to generate more descriptive and contextually relevant titles for content catalogs. This allows for dynamic catalog naming based on user preferences and content attributes, making the browsing experience more intuitive and engaging. Additionally, it refines the caching strategy for catalog responses and introduces translation capabilities for catalog names, improving both performance and localization.

Highlights

  • Gemini AI Integration: A new Gemini AI service has been introduced to dynamically generate more natural and engaging titles for content catalogs, moving away from simple concatenated names.
  • Dynamic Catalog Naming: The catalog row generation logic now leverages the Gemini AI to create titles based on various criteria such as combined keywords, genre and keyword, genre and country, and genre and decade, with fallback mechanisms if AI generation is unsuccessful.
  • Conditional Caching: The API endpoint for retrieving catalogs now intelligently sets the Cache-Control header to 'no-cache' if no recommendations are returned, preventing the caching of empty responses.
  • Catalog Translation: Catalog names are now translated based on user language settings, enhancing localization for dynamic catalogs.
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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new feature to generate catalog names using the Gemini AI service, which is a great addition for creating more engaging user experiences. The implementation includes adding the necessary configuration, a new Gemini service, and integrating it into the row generation logic with fallbacks, which is a robust approach.

I've identified a few issues that need attention. There's a critical bug in row_generator.py that could cause an IndexError, and a high-severity issue in catalog_updater.py that might lead to data loss. Additionally, there's a design concern in gemini.py where the application could crash if the optional API key isn't provided. I've also included a medium-severity comment to clean up some debug code. My suggestions aim to fix these issues and improve the overall robustness of the new feature.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@TimilsinaBimal
Copy link
Owner Author

/gemini review

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new Gemini service to generate catalog names. The implementation of the Gemini service has some critical issues with how the SDK is used, which will likely cause it to fail at runtime. I've provided suggestions to fix the SDK usage. Additionally, there's an opportunity to refactor some duplicated code in the row generator for better maintainability, and some unused code in the new Gemini service file that can be cleaned up.

@TimilsinaBimal
Copy link
Owner Author

/gemini review

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a Gemini service for generating more natural catalog names and adds a translation feature. The core changes are in app/services/gemini.py and app/services/row_generator.py. My review identified a critical issue in gemini.py where a deprecated and incorrect API is used, which will cause the feature to fail. I've suggested a refactor to use the modern async API. Consequently, the calls to the Gemini service in row_generator.py are synchronous and should be awaited. I've also pointed out a minor maintainability issue in row_generator.py regarding verbose and duplicated code. The other changes, including dependency updates and caching logic, appear to be in good order.

@TimilsinaBimal TimilsinaBimal merged commit 5e7bf53 into dev Dec 10, 2025
4 checks passed
@TimilsinaBimal TimilsinaBimal deleted the feat/ai-name-generation branch December 10, 2025 08:10
TimilsinaBimal added a commit that referenced this pull request Dec 12, 2025
* feat: add option to rename, disable, reorder catalogs

* feat: new recommendation system based on weights

* feat: dynamic row generator

* feat: add dynamic row generator with country flag

* feat: add watched.loved row

* feat: new ui with stremio auth button

* feat: add languages selection button in ui for tmdb meta

* feat: add option to enable rpdb api key for posters

* feat: ui improvements

* chore: add vercel app env

* chore: improve recommendation weights and refactor

* chore: remove unnecessary country flags

* add workflows to bump version

* chore: bump version to 1.0.0-rc.1

* chore: bump version to 1.0.0-rc.2

* chore: use redis token from config

* fix: priotrize keywords for row generation than genre

* chore: bump version to v1.0.0-rc.3

* feat: add option to delete account

* refactor: update token deletion API to use DELETE / and implement deep cloning for catalog data in the frontend, removing conditional name handling.

* opt: improve recommendations using larger candidate pool and better similarity methods

* feat: Add genre exclusion UI, store excluded genres in user settings,and apply them during catalog generation (#21)

* feat: Add genre exclusion UI, store excluded genres in user settings, and apply them during catalog generation.

* refactor: simplify filtering recommendations by excluded genres using list comprehension

* refactor: streamline genre exclusion logic for similarity recommendations

* feat: Rework UI into a multi-step setup wizard with account management and section navigation (#22)

* feat: Rework UI into a multi-step setup wizard with Watchly account management and section navigation
* critical: check if user already exists

* refactor: remove disabled class from source code button

* feat: add translation service to translate catalog names to user language (#23)

* feat: add option to rename, enable disable catalogs (#24)

* feat: Implement user ID-based token management and Stremio user info fetching, replacing credential-derived tokens and direct login. (#25)

* refactor: code refactoring and remove legacy code and components (#26)

* feat: add option to rename, enable disable catalogs

* feat: add option to rename, enable disable catalogs

* feat: Implement user ID-based token management and Stremio user info fetching, replacing credential-derived tokens and direct login.

* feat: Implement user ID-based token management and Stremio user info fetching, replacing credential-derived tokens and direct login.

* feat: Refactor token management to use a dedicated token model, remove token salt, and streamline catalog refresh logic.

* feat: Encrypt auth keys in token store and enforce 401 for invalid tokens across endpoints.

* feat: Introduce token redaction utility and apply it to log messages for enhanced security.

* feat: Introduce token redaction utility and apply it to log messages for enhanced security.

* fernet client management

* feat: add migration script to migrate old tokens to new system

* feat: check and only update tokens that are installed from the same system

* opt: give more weight to items watched recently

* docs: add contributing guidelines and acknowledgements

* opt: optimize translation service

* chore: bump version to v1.0.0-rc.6

* feat: add gemini service to generate catalog names (#29)

* Refactor services for improved async handling and error resilience (#30)

* refactor: fetch loved and liked items at once and use that

* Refactor services for improved async handling and error resilience

* chore: bump version to v1.0.0

* feat: better bare row name generation (#32)
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.

2 participants