Skip to content

fix(gpui): keep a typed AI Core deployment mapping on save - #233

Merged
stippi merged 1 commit into
mainfrom
fix/ai-core-pending-deployment
Oct 8, 2026
Merged

stippi merged 1 commit into
mainfrom
fix/ai-core-pending-deployment

Conversation

@daniel-kurzynski

Copy link
Copy Markdown
Collaborator

Problem

In the AI Core provider form, a model-to-deployment mapping is only added to the form once its add button is clicked. If you fill in the add row (model ID, deployment ID, API type) and press Save straight away, the mapping is silently dropped. The form closes on save, so you only notice when you open the provider again.

Change

AiCoreProviderForm::to_config_json now also saves a fully filled add row (model ID and deployment ID, trimmed) with its selected API type, unless a mapping for that model already exists in the list.

Tests

  • a_mapping_typed_but_not_added_is_saved: a filled add row ends up in models with its deployment and API type.
  • an_added_mapping_wins_over_the_add_row: a row for a model that is already mapped doesn't replace the existing mapping.

A model-to-deployment mapping becomes part of the AI Core provider form
only when its add button is clicked. A mapping typed into the add row
and saved right away was dropped without notice, and the form closes on
save, so the loss showed only when the provider was opened again.

Saving now includes a fully typed add row (model ID and deployment ID)
unless a mapping for that model already exists.
@stippi
stippi merged commit f19e4b6 into main Oct 8, 2026
5 checks passed
@stippi
stippi deleted the fix/ai-core-pending-deployment branch October 8, 2026 18:20
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