-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
elasticsearch-plugin: Allow custom sort parameter input #1220
Comments
Draykee
pushed a commit
to Draykee/vendure
that referenced
this issue
Nov 17, 2021
Hi, could this not be solved with the existing ExtendSearchInputType option, combined with mapQuery? |
No this is not possible.
|
OK got it, thanks for clarifying. I'll review the PR later today 👍 |
michaelbromley
pushed a commit
that referenced
this issue
Nov 23, 2021
Closes #1220 * feat(elasticsearch-plugin): Added custom sort parameter mapping (#1220) * fix(elasticsearch-plugin): Removed unwanted change of price and name sort Co-authored-by: Kevin <[email protected]>
Resolved with: #1230 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently we can only sort by price and name using the elasticsearch plugin.
Those fields are then hardcoded and parsed into the
sort
field of the elasticseach request body.Describe the solution you'd like
I would like to have an option to push additional sort parameters to the
sortArray
. I guess the only way to do that is another option inside thesearchConfig
configuration.The biggest problem is that we are not able to extend a graphQL input (defined in
packages/core/src/api/schema/common/common-types.graphql
). Maybe a search plugin needs to define those to generate them at runtime?Describe alternatives you've considered
I'm not sure if we are able to apply sorting within the query, but if not there is no alternative.
The text was updated successfully, but these errors were encountered: