Skip to content

Handle unknown models#104

Merged
AnthonyRonning merged 1 commit intomasterfrom
unknown-models
Jun 10, 2025
Merged

Handle unknown models#104
AnthonyRonning merged 1 commit intomasterfrom
unknown-models

Conversation

@AnthonyRonning
Copy link
Contributor

@AnthonyRonning AnthonyRonning commented Jun 10, 2025

Summary by CodeRabbit

  • New Features

    • Added "Gemma 3 27B" as a new model option, marked as "Coming Soon" and currently disabled in the model selector.
  • Refactor

    • Enhanced model dropdown display to show a "Coming Soon" badge for unknown models and disable their selection consistently.

@coderabbitai
Copy link

coderabbitai bot commented Jun 10, 2025

Walkthrough

The update refactors the model selection logic in the ModelSelector component. It adds a new "Gemma 3 27B" model as disabled and "Coming Soon," unifies how display names and badges are rendered for both known and unknown models, and ensures unknown models are always shown as disabled with a "Coming Soon" badge in the dropdown.

Changes

File(s) Change Summary
frontend/src/components/ModelSelector.tsx Added new disabled model entry; refactored display name logic; unknown models show "Coming Soon" badge and are disabled in dropdown.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ModelSelector
    participant MODEL_CONFIG

    User->>ModelSelector: Open model dropdown
    ModelSelector->>MODEL_CONFIG: Fetch model list
    ModelSelector->>ModelSelector: For each model:
    alt Model exists in MODEL_CONFIG
        ModelSelector->>ModelSelector: Show display name and badges
        alt Model is disabled
            ModelSelector->>User: Show as disabled with badge
        else Model is enabled
            ModelSelector->>User: Show as selectable
        end
    else Model not in MODEL_CONFIG
        ModelSelector->>User: Show model ID with "Coming Soon" badge, disabled
    end
Loading

Poem

A new Gemma hops into view,
"Coming Soon"—not yet for you!
Badges now shine for all to see,
Even unknowns get their spree.
Dropdowns unified, no more gloom,
Models sorted, badges bloom!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7ac591d and 6e34264.

📒 Files selected for processing (1)
  • frontend/src/components/ModelSelector.tsx (5 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • frontend/src/components/ModelSelector.tsx
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: browseruse-tests
  • GitHub Check: build-macos (universal-apple-darwin)
  • GitHub Check: build-linux
  • GitHub Check: Cloudflare Pages
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 902e322 and 7ac591d.

📒 Files selected for processing (1)
  • frontend/src/components/ModelSelector.tsx (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: build-macos (universal-apple-darwin)
  • GitHub Check: build-linux
  • GitHub Check: build-ios
  • GitHub Check: browseruse-tests
🔇 Additional comments (5)
frontend/src/components/ModelSelector.tsx (5)

123-127: Good refactor to unify display logic.

The change to always build an array of React elements provides consistent handling for both known and unknown models, improving maintainability.


149-161: Excellent handling of unknown models.

The implementation correctly ensures unknown models are displayed with proper context (model ID + "Coming Soon" badge) while maintaining visual consistency with the rest of the UI.


192-194: Appropriate default behavior for unknown models.

Treating unknown models as disabled by default is a sensible approach that prevents users from selecting potentially non-functional models while still displaying them for transparency.


210-211: Consistent disabled state logic.

The logic correctly mirrors the sorting behavior and ensures unknown models are properly disabled in the dropdown interface.


163-163:

Details

✅ Verification successful

Verify type compatibility with existing usage.

The function now always returns JSX instead of potentially returning a string. Ensure all callers of getDisplayName expect React elements.


🏁 Script executed:

#!/bin/bash
# Search for all usages of getDisplayName to verify compatibility
rg -A 3 -B 3 "getDisplayName" --type tsx --type ts

Length of output: 78


🏁 Script executed:

#!/bin/bash
# Search for all usages of getDisplayName across TS and TSX files without relying on predefined types
rg -n "getDisplayName" -g '*.ts' -g '*.tsx' -C 3

Length of output: 1907


No action needed: getDisplayName usages accept React nodes

I’ve verified that all calls to getDisplayName (lines 170 and 234 in ModelSelector.tsx) occur within JSX and treat its return value as a ReactNode. Since strings and JSX elements are both valid ReactNodes, the change is fully compatible.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jun 10, 2025

Deploying maple with  Cloudflare Pages  Cloudflare Pages

Latest commit: 6e34264
Status: ✅  Deploy successful!
Preview URL: https://79c15c46.maple-ca8.pages.dev
Branch Preview URL: https://unknown-models.maple-ca8.pages.dev

View logs

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

Enhanced model selector to gracefully handle unknown AI models, with specific improvements for future model compatibility.

  • Added robust handling of unknown models in frontend/src/components/ModelSelector.tsx with 'Coming Soon' badge display
  • Implemented sorting logic to place disabled/unknown models at the end of the dropdown list
  • Added new Gemma 3 27B model configuration as a disabled preview option
  • Refactored getDisplayName function to use React elements array for more flexible model name rendering

1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile

@AnthonyRonning AnthonyRonning merged commit da61211 into master Jun 10, 2025
7 checks passed
@AnthonyRonning AnthonyRonning deleted the unknown-models branch June 10, 2025 16:26
@coderabbitai coderabbitai bot mentioned this pull request Feb 20, 2026
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.

1 participant