You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the search parametershowRankingScoreDetails. We should be able to use it with the search() method.
Here are the JS equivalents in meilisearch-js you should create for this repository:
556: Add parameter to show ranking score details to the search query r=curquiza a=gudmunduro
# Pull Request
## Related issue
Fixes#530
## What does this PR do?
- Adds the showRankingScoreDetails parameter to the search query
## PR checklist
Please check if your PR fulfills the following requirements:
- [x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
- [x] Have you read the contributing guidelines?
- [x] Have you made sure that the title is accurate and descriptive of the changes?
Thank you so much for contributing to Meilisearch!
559: Update version for the next release (v0.15.3) r=curquiza a=meili-bot
_This PR is auto-generated._
The automated script updates the version of meilisearch-dotnet to a new version: "v0.15.3"
Co-authored-by: gudmunduro <goh00@protonmail.com>
Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com>
Following this central issue
This is related to a newly introduced feature in Meilisearch v1.7.0: show ranking score details at search.
Refer to docs for more information.
showRankingScoreDetails
. We should be able to use it with thesearch()
method.Here are the JS equivalents in meilisearch-js you should create for this repository:
_rankingScoreDetails
key/value in the search hits' response..code-samples.meilisearch.yaml
search_parameter_guide_show_ranking_score_details_1
key and “translate” the following curl example by using the newly added changes: https://github.com/meilisearch/documentation/blob/090717049e117ffaa3a54baa010883c1c5f90c31/.code-samples.meilisearch.yaml#L1103-L1110The text was updated successfully, but these errors were encountered: