Repository navigation
fix: honor lite as default search type - #466
Merged
Merged
Conversation
kesku
force-pushed
the
kesku/default-search-type-lite
branch
from
October 28, 2026 19:24
daf8af1 to
60be677
Compare
wlue
approved these changes
Oct 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Fixes an issue where configuring
liteas the default search type silently falls back toautoin the MCP server.litealongsideauto,fast, andinstantfor HTTP?defaultSearchType=and theDEFAULT_SEARCH_TYPEenvironment variable.Behavior
liteis now forwarded correctly when configured as the default search type.autoremains the default when no valid search type is configured.fastandinstantconfigurations continue working unchanged.Testing
npm run cigit diff --check