fix(frontend): set v1_enable correctly when saving mcp settings #11948
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 of PR
Description:
If v1_enable is manually set to true in the database and a user subsequently opens the UI and saves the MCP settings, the v1_enable field is automatically changed to false, even when no update to this field was intended.
Acceptance Criteria:
Change Type
Checklist
Fixes
Resolves #(issue)
Release Notes
To run this PR locally, use the following command:
GUI with Docker: