-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Meilisearch double quote on "match" query #29740
Conversation
PS: yes t hat would be even better ... |
Yeah, that's the idea. The only downside I see with this "double-quote everything" solution is that you cannot parse the same way as Meilisearch, and that's why the "expose the I just talked about this to our Product manager and they will prioritize this. However, we don't refer to typo tolerance as fuzziness so I was a bit confused 😄 |
@Kerollmops that's awesome ❤️ I hope to get the code-search ready for meilisearch too and at that point we should have a really good integration 🚀 |
well with this patch if I search for
it wont find it anymore but I think that's ok as #29701 will let the user decide if he want it fuzzy (typoTolerance) or not thanks in advance to @Kerollmops for pointing out how to tell meilisearch to do so PS: a space in the example case would fix it:
|
@Kerollmops for the |
Thank you for the PR @6543. We will take care of it later this or next week 🙂 |
Can you have a ref doc link for the quote behaviours? |
275: Support markdown formatted codeblocks r=ManyTheFish a=6543 # Pull Request ## Related issue Fixes go-gitea/gitea#29740 (comment) ## What does this PR do? add ``` ` ``` as seperator to support markdown formated text ## PR checklist Please check if your PR fulfills the following requirements: > Does this PR fix an existing issue, or have you listed the changes applied in the PR description... well I can file a issue if desired but I think this is a minor change? - [x] Have you read the contributing guidelines? - [x] Have you made sure that the title is accurate and descriptive of the changes -> I hope so ;) Co-authored-by: 6543 <6543@obermui.de>
I was unable to create a backport for 1.21. @6543, please send one manually. 🍵
|
make `nonFuzzyWorkaround` unessesary cc @Kerollmops
* giteaofficial/main: (28 commits) Forbid jQuery `.prop` and fix related issues (go-gitea#29832) Fix wrong test for TestPullView_CodeOwner (go-gitea#29838) Forbid HTML injection using jQuery (go-gitea#29843) Meilisearch double quote on "match" query (go-gitea#29740) Forbid variables containing jQuery collections not having the `$` prefix (go-gitea#29839) Remove AddParamIfExist(AddParam) (go-gitea#29841) Refactor markdown attention render (go-gitea#29833) Refactor code_indexer to use an SearchOptions struct for PerformSearch (go-gitea#29724) Refactor AddParam to AddParamIfExist (go-gitea#29834) Forbid jQuery AJAX (go-gitea#29818) Remove jQuery AJAX from the notifications (go-gitea#29817) Light theme color enhancements (go-gitea#29830) Better highlighting of archved labels (go-gitea#29749) Remove the `time-since` class (go-gitea#29826) Remove jQuery AJAX from the project page (go-gitea#29814) Upgrade `htmx` to v1.9.11 (go-gitea#29821) Dark theme color enhancements (go-gitea#29822) Remove jQuery AJAX from the comment edit box (go-gitea#29812) Tweak labeler (go-gitea#29809) Fix `for` attribute not pointing to the ID of the color picker (go-gitea#29813) ... # Conflicts: # routers/web/user/home.go
Backport go-gitea/gitea#29740 (based on #29671 ...) (cherry picked from commit 0cbbcf20e3f83413a88fe3d436451d707639fe55)
make
nonFuzzyWorkaround
unessesarycc @Kerollmops