Context
Meilisearch v1.50.0 introduces a revamped Dynamic Search Rules (also called "search rules") experimental feature. Search rules allow pinning documents at the top of search results when flexible, condition-based criteria are matched — such as matching query words, empty queries, or time windows.
This is an experimental feature and must be enabled via PATCH /experimental-features with {"dynamicSearchRules": true} before the endpoints are available.
Objective
Update the SDK to support the search rules API.
We want to expose the following endpoints:
- List rules:
POST /dynamic-search-rules
- Get a rule:
GET /dynamic-search-rules/{uid}
- Create or update a rule:
PATCH /dynamic-search-rules/{uid} (upsert — returns an async task)
- Delete a rule:
DELETE /dynamic-search-rules/{uid} (returns an async task)
For more information, consult:
Tasks
Context
Meilisearch v1.50.0 introduces a revamped Dynamic Search Rules (also called "search rules") experimental feature. Search rules allow pinning documents at the top of search results when flexible, condition-based criteria are matched — such as matching query words, empty queries, or time windows.
This is an experimental feature and must be enabled via
PATCH /experimental-featureswith{"dynamicSearchRules": true}before the endpoints are available.Objective
Update the SDK to support the search rules API.
We want to expose the following endpoints:
POST /dynamic-search-rulesGET /dynamic-search-rules/{uid}PATCH /dynamic-search-rules/{uid}(upsert — returns an async task)DELETE /dynamic-search-rules/{uid}(returns an async task)For more information, consult:
Tasks
list,get,updateOrCreate,delete)PATCHandDELETEcorrectly return and handle async tasks.code-samples.meilisearch.yamlto add examples under the following keys:list_dynamic_search_rules_1— it should match the equivalent documentation sampleget_dynamic_search_rule_1— it should match the equivalent documentation samplepatch_dynamic_search_rule_1— it should match the equivalent documentation sampledelete_dynamic_search_rule_1— it should match the equivalent documentation sample