Fix issue #6940: [Bug]: Incorrect Provider Name on Advanced Setting Toggle #6941
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 pull request fixes #6940.
The issue has been successfully resolved based on the following concrete changes and their effects:
handleChangeProvider
function to properly map display names to internal provider keys. When "Mistral AI" is selected, it now correctly maps to "mistral" internally through the new lookup logic:The changes ensure that the internal state uses the correct provider key ("mistral") while maintaining the display name ("Mistral AI") in the UI, preventing the settings page from incorrectly switching to advanced mode.
The fix was verified with a new test case that specifically checks the Mistral AI provider selection workflow, confirming:
The changes directly target and resolve the reported behavior problems through proper provider name handling and state management.
Automatic fix generated by OpenHands 🙌
To run this PR locally, use the following command: