meilisearch/meilisearch-dotnet

The tests are failing when run against Meilisearch v1.54, see failing tests.

Context Meilisearch v1.53.0 adds indexSize and usedIndexSize to per-index stats. Objective Update the SDK so index stats responses include the new indexSize and usedIndexSize fields returned by Get stats of index and per index in Get stats of all indexes. indexSize: size of the index DB (bytes by default; honour sizeFormat when supported) usedIndexSize: size of the used pages of the index DB (bytes by default; honour sizeFormat when supported) Tasks Add indexSize and usedIndexSize to the index stats response shape Update test cases

Context Meilisearch v1.51.0 introduces filter conditions for Dynamic Search Rules (DSR). It also introduces a new lastUpdatedAt field in DSR responses. Objective Update the SDK to support: The new filter activation condition in the conditions object of a DSR. The filter condition contains a values key whose value is a JSON object mapping facet names to their expected filter values. The new lastUpdatedAt field returned by GET /dynamic-search-rules/{:ruleUid} and POST /dynamic-search-rules. Use these resources: Release notes Search Rules Overview — API reference Example of a DSR with a filter condition // PATCH /dynamic-search-rules/test-filter { "conditions": { "filter": { "values": { "color": "red", "category": "shirt" } } }, "actions": [ { "selector": { "indexUid": "products", "id": "123" }, "action": { "type": "pin", "position": 1 } } ] } Tasks Update the conditions parameter to accept the n

Context Meilisearch v1.50.0 revamps the Dynamic Search Rules (DSR) experimental feature with breaking changes to the API. This SDK already shipped the initial v1.41 implementation and must be updated to match the new schema and behavior. WarningThe Dynamic Search Rules API in meilisearch-dotnet v0.19 and v0.20 is incompatible with Meilisearch v1.50+ Request type changes priority → precedence: Renamed to better reflect behavior (lower precedence = applied first). conditions restructured: Changed from an array of { scope, ... } objects to a structured object with two keys: query: a QueryCondition containing isEmpty?: boolean and words?: string[] time: a TimeCondition containing start?: string and end?: string (ISO 8601) contains → words: Query matching is now word-based instead of substring-based. A rule matches if all words in conditions.query.words appear in the search query (after normalization). isEmpty: false can now be combined with words. id now mandatory in the selector

Context Meilisearch introduced document relations as an experimental feature. Objective Add support for the document relations settings as an experimental feature. Experimental features should require opt-in by the user. Read the how to guide for more information. Tasks Add methods to interact with Get foreignKeys, Update foreignKeys, and Reset foreignKeys API endpoints Update the global settings methods to accept and handle the foreignKeys setting Add test cases for all new methods Add code samples in .code-samples.meilisearch.yaml matching the Meilisearch documentation CURL examples: Under get_foreign_keys_setting_1: equivalent of this code sample Under update_foreign_keys_setting_1: equivalent of this code sample Under reset_foreign_keys_setting_1: equivalent of this code sample Resources Release notes: Meilisearch v1.39 introduced cross-index document hydration via a new foreignKeys index setting. This allows linking documents across indexes so that search results are