fix(ui-tars): allow VLM key fields from multiple sources during preset import #533
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes an issue where importing preset configurations would fail if any of the three VLM key fields (
vlmBaseUrl
,vlmApiKey
, andvlmModelName
) were missing, even if they were already set in the Settings-VLM settings page.The changes allow these key fields to be provided from either source (Settings-VLM page or imported configuration), improving user experience by making the validation less strict. As long as one source provides the necessary values, the application will function correctly.
Key changes:
PresetSchema
to make VLM key fields optionalmergeWithExistingSettings
function to combine settings from multiple sourcesimportPresetFromText
to merge imported settings with existing onesCloses: #532
Checklist