fix: prevent TypeError when switching providers after model selection #9049
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.
This PR fixes issue #9047 where switching providers after selecting a model causes a TypeError.
Problem
When users switch providers after selecting a model, the router models for the new provider may not be loaded yet, causing a TypeError when the code tries to access properties on undefined objects.
Solution
Added optional chaining (
?.) to all router model accesses in theuseSelectedModelhook to safely handle cases where router models are undefined during provider transitions.Changes
Testing
Fixes #9047
Important
Fixes TypeError when switching providers after model selection by adding optional chaining to router model accesses in
useSelectedModel.?.) to router model accesses inuseSelectedModel.openrouter,requesty,glama,unbound,litellm,chutes, androo.This description was created by
for fd6c987. You can customize this summary. It will automatically update as commits are pushed.