fix: support multi-word plugin search - #284
Open
yashkhatri012 wants to merge 1 commit into
Open
Conversation
Contributor
🟠 Maintainer review suggested — low confidenceThe automated review could not reach a fully supported conclusion. This review is advisory and does not block merging. |
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
1 participant
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.
What
Fixes multi-word plugin searches by normalizing query tokens and requiring all tokens to match the plugin name/description.
Example
Previously:
webcmd plugin search "hacker news"→ no resultsNow:
webcmd plugin search "hacker news"→ findshackernewsAlso handles separator variants such as
hacker-news.Tests
npx vitest run src/plugin-catalog.test.ts— 9/9 passingnpm run typecheck— passingFixes #282