This issue follows the changes related to Meilisearch v1.14.0 mega issue.
Update the settings API to handle the new filterableAttributes syntax.
For more context, see the related issue in Meilisearch: https://github.com/meilisearch/meilisearch/issues/5163
filterableAttributes syntaxfilterableAttributes syntax (when Meilisearch returns it)update_filterable_attributes_1 code sample in .code-samples.meilisearch.yamlFor reference, here's how the test are implemented in Meilisearch JS SDK:
// this mixes the old syntax (field name) and new syntax (settings opt-in)
const newFilterableAttributes = [
"author",
{
attributePatterns: ["genre"],
features: {
facetSearch: true,
filter: { equality: true, comparison: false },
},
},
];
// we update the filterable attributes settings
await client
.index(index.uid)
.updateFilterableAttributes(newFilterableAttributes)
.waitTask();
// the method to retrieve filterable attributes settings can also return mixed syntax
const response = await client.index(index.uid).getFilterableAttributes();
expect(response).toEqual(newFilterableAttributes);