fix(studio): Add a model dropdown for Base Model filtering on the Virtual Model Grid

[htolentino-nvidia]

https://linear.app/nvidia/issue/ASTD-307/virtual-models-default-model-filter-is-a-free-text-input-with-no

Summary by CodeRabbit

• New Features

  • Added a dedicated “Default Model” filter with single-select search behavior.

• Bug Fixes

  • Improved filtering accuracy by matching the selected default model exactly.
  • Ensured model-related column displays stay synchronized with the current workspace.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f4d78ad0-a404-49b3-aa6a-99413e470599

📥 Commits

Reviewing files that changed from the base of the PR and between 8a5663f and 41226b0.

📒 Files selected for processing (1)

• web/packages/studio/src/components/dataViews/VirtualModelsDataView/index.tsx

---

📝 Walkthrough

Walkthrough

VirtualModelsDataView replaces the Default Model text filter with a single-select model search field, applies exact $eq filtering, and includes workspace in column memoization dependencies.

Changes

Virtual model filtering

Layer / File(s)	Summary
Default model filter integration web/packages/studio/src/components/dataViews/VirtualModelsDataView/index.tsx	The Default Model column renders BaseModelSearchFilterField, stores one selected model or undefined, applies default_model_entity with $eq, and rebuilds columns when workspace changes.

Possibly related PRs

• NVIDIA-NeMo/nemo-platform#689: Adds the VirtualModel filtering support that includes default_model_entity.

Suggested labels: feat

Suggested reviewers: shanaiabuggy

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding a model dropdown for Base Model filtering in the Virtual Model Grid.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ASTD-307-fix-base-model-filters/htolentino

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Suite	Lines Covered	Line Rate	Branch Rate
Unit Tests	25534/32732	78.0%	62.7%
Integration Tests	14730/31381	46.9%	19.3%

[steramae-nvidia]

why the change from $like to $eq?

[htolentino-nvidia]

Good question @steramae-nvidia, I do think when the user selects a specific model on the dropdown they wouldn't expect to see models that would be also matched by $like, since they clicked llama-8b for example (and not any other llama variant on the dropdown) I wouldn't want to display base models like llama-8b-custom-ft. Now, this was requested by QA, I'm not super sure the dropdown for this type of filtering is the more useful pattern here. The user can't really filter by all nemotron models if they wanted so, but at least here we're matching the existing behaviour on in the custom models page.