-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: make full text search default #10626
Conversation
098ba79
to
a0d5ccd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same logic as in the search result page should also apply for the search preview.
const fullTextParam = useRouteQuery('q_fullText') | ||
const titleOnlyParam = useRouteQuery('q_titleOnly') | ||
|
||
const fullTextSearchEnabled = computed(() => capabilityStore.searchContent?.enabled) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not using storeToRefs for that ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because it's nested in the capabilities, meaning even if we'd use storeToRefs
, we would still need to further narrow it down via a computed
.
c1b28de
to
f9c97ca
Compare
Okay, now it searches for I decided to remove the generic query building we had before because it didn't really allow edge cases like we have here. |
Enables full text search as default if the server supports it.
f9c97ca
to
bc052dd
Compare
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥳
Description
Enables full text search as default if the server supports it.
Related Issue
Types of changes