Open
Conversation
Proposed behavior : Fuzzy search on title (same as actual behavior) + precise search on description (not using the fuzzy search function because it will return too many results for description field)
|
|
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
2 participants
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.
Problem:
While looking for extensions in the shop, I couldn't find one that allows articles to be exported to Hugo (I tried searching with the keywords "Hugo" and "export"). I had to search online and found that the extension is called "logseq-schrodinger". I would never have thought to search for something like that! However, the keywords were present in the description: "An awesome logseq plugin to export to Hugo Static sites and jumpstart your digital garden 🌱!"
Another example would be searching for the word "mind" and not having the most popular mind map extension in Logseq, Markmap, in the results. This wouldn't be the case if this PR is accepted.
I first tried doing a fuzzy search on the title and description, but a fuzzy search on the description field was a bad idea as too many results were returned (which is logical).
Proposed behavior:
Combined result (without duplicate) of fuzzy search on title (same as current behavior) + precise search on description (if it exists)