Reduce lexical search result limit and field weights#2467
Merged
Mbeaulne merged 1 commit intoJun 29, 2026
Conversation
🎩 PreviewA preview build has been created at: |
Collaborator
Author
This was referenced Jun 29, 2026
This was referenced Jun 29, 2026
morgan-wowk
approved these changes
Jun 29, 2026
Collaborator
Author
Merge activity
|
fe16ad3 to
4c1dd36
Compare
4c1dd36 to
debaf99
Compare
8 tasks
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.

Description
Reduces the default number of displayed search results from 50 to 10, applying the
LEXICAL_RESULT_LIMITcap to both lexical and reranked match lists so users see a focused set of results before opting into AI judgment.Additionally, lowers the scoring weights for
implementationandmetadatafields significantly —implementationbase weight drops from 1 to 0.25 and its phrase bonus from 2 to 0.5 — so that incidental keyword matches in command comments or container args no longer surface above results where the word appears in a component's name, description, or inputs/outputs.Related Issue and Pull requests
Type of Change
Checklist
Screenshots (if applicable)
Test Instructions
train). Confirm no more than 10 results are shown before triggering AI search.componentSearchV2Logic.test.tsandcomponentSearchIndex.test.tspass.Additional Comments
The
LEXICAL_RESULT_LIMITconstant is now exported fromcomponentSearchV2Logic.tsso it can be referenced directly in tests to keep the cap assertion resilient to future value changes.