Fix planner_llm_model_name
Not Loaded Correctly When Using "Load Config"
#590
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.
Solution
planner_llm_provider
before setting the model name.planner_llm_model_name
, dynamically update its choices based on the provider, and usegr.Dropdown(value=..., choices=..., allow_custom_value=True)
to update the component.Impact
Testing
Screenshot
Reference
fix #589
Summary by mrge
Fixed the "Load Config" feature so the planner LLM model name dropdown now shows the correct model based on the selected provider.