-
Couldn't load subscription status.
- Fork 13
Moved relevance query to default query value #1049
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
Open
indykoning
wants to merge
5
commits into
master
Choose a base branch
from
feature/allow-overriding-relevance-query
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+23
−14
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3f0e4c7
Moved relevance query to default query value
indykoning 70f667d
Apply fixes from Prettier
indykoning ec7d294
[CI] Update Snapshots
indykoning 4a7b196
Discard changes to resources/js/package.js
indykoning 69d5587
[CI] Update Snapshots
indykoning File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,6 +5,17 @@ import { instantsearchMiddlewares } from '../../stores/useInstantsearchMiddlewar | |
| import { createInsightsMiddleware } from 'instantsearch.js/es/middlewares/createInsightsMiddleware' | ||
| export default { | ||
| props: { | ||
| query: { | ||
| type: Function, | ||
| default: function (query, searchAttributes, config) { | ||
| // __NO_QUERY__ is a temporary band-aid for https://github.com/searchkit/searchkit/pull/1407 | ||
| if (query && query !== '__NO_QUERY__') { | ||
| return this.relevanceQueryMatch(query, searchAttributes, config?.fuzziness) | ||
| } | ||
| }, | ||
| }, | ||
| }, | ||
| data: () => ({ | ||
| searchkit: null, | ||
| searchClient: null, | ||
|
|
@@ -45,6 +56,7 @@ export default { | |
| }) | ||
| }, | ||
| }, | ||
| getQuery: this.getQuery, | ||
| } | ||
| }, | ||
|
|
@@ -56,6 +68,13 @@ export default { | |
| return instantsearchMiddlewares | ||
| }, | ||
| getQuery(query, search_attributes, config) { | ||
| const esQuery = this.query(...arguments) | ||
| let queries = Array.isArray(esQuery) ? esQuery : [esQuery] | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This check just makes sure it's backwards compatible with the old way of returning an array of queries instead of a query on it's own |
||
| return queries.filter((q) => q) | ||
| }, | ||
| relevanceQueryMatch(query, search_attributes, fuzziness = 'AUTO:4,8') { | ||
| // Copied from searchkit.js default behavior when getQuery is not defined. | ||
| const getFieldsMap = (boostMultiplier) => { | ||
|
|
||
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.
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.
We could still move this to the getQuery function, removing the ability to remove/move the
relevanceQueryMatchwhich hasn't been an ability yet until now.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.
I don't necessarily mind this approach, but now if you want to add an extra query to this (for example, some kind of extra scoring function) you will also need to re-define this functionality inside of the prop. Seems a bit unwieldy to me for those cases.
Might be better in practice to have a prop that lets you disable the default query?