Conversation
Summary of ChangesHello, 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 enhances the model registration service by aligning the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request extends the model registration for Codex to include the 'business' plan type, treating it the same as the 'team' plan type. The change is straightforward and correct. My main feedback is to add a unit test to cover this new logic to prevent future regressions and ensure maintainability.
| case "plus": | ||
| models = registry.GetCodexPlusModels() | ||
| case "team": | ||
| case "team", "business": |
There was a problem hiding this comment.
While this change correctly handles the 'business' plan type, this part of the model registration logic appears to be untested. To ensure the correctness of this new addition and prevent future regressions, it would be beneficial to add a unit test.
You could create a test that:
- Initializes a
Service. - Creates a
coreauth.Authobject withProvider: "codex"andAttributes: map[string]string{"plan_type": "business"}. - Calls
service.registerModelsForAuth()with this auth object. - Asserts that the models from
registry.GetCodexTeamModels()are registered for the auth ID in theGlobalModelRegistry().
This would provide good test coverage for the change.
No description provided.