Add the filterableAttributes field to the Strapi interface

[DoctorPok42]

Description
After selecting a collection to index, you can select the fields in the collection to filter.

Basic example
For example, with this ‘posts’ collection.
Once indexed, I would like to have a ‘filter’ submenu with the attributes of the collection that I could check.
Once the submenu is expanded, I can check the slug attribute in the categories element.

After that, if I run this query:
GET http://localhost:7700/indexes/post/settings/filterable-attributes

it will give me this:

[
  "categories.slug"
]

The collection schema:

{
  "kind": "collectionType",
  "collectionName": "posts",
  "info": {
    "singularName": "post",
    "pluralName": "posts",
    "displayName": "Post"
  },
  "options": {
    "draftAndPublish": true
  },
  "pluginOptions": {
    "i18n": {
      "localized": true
    }
  },
  "attributes": {
    "..."
    "categories": {
      "type": "relation",
      "relation": "manyToMany",
      "target": "api::category.category",
      "mappedBy": "posts"
    },
    "..."
}

{
  "kind": "collectionType",
  "collectionName": "categories",
  "info": {
    "singularName": "category",
    "pluralName": "categories",
    "displayName": "Category"
  },
  "options": {
    "draftAndPublish": true
  },
  "pluginOptions": {
    "i18n": {
      "localized": true
    }
  },
  "attributes": {
    "name": {
      "type": "string",
      "pluginOptions": {
        "i18n": {
          "localized": true
        }
      },
      "minLength": 3,
      "required": true
    },
    "slug": {
      "type": "uid",
      "pluginOptions": {
        "i18n": {
          "localized": true
        }
      },
      "targetField": "name",
      "required": true,
      "minLength": 3
    },
  }
}

I would like to develop this feature.
Could a maintainer check if it would be useful to you before I get started?

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Strift]

Hello @DoctorPok42, and thanks for considering contributing to Meilisearch. 🙌

Updating settings from the UI

Your idea raises a ‘source of truth’ issue. The plugin should ideally fetch settings from the instance rather than trying to replicate the full configuration logic inside Strapi.

Meilisearch Cloud is the preferred way to configure settings. Open-source alternatives like [meilisearch UI]https://github.com/eyeix/meilisearch-ui) also exist.

Reading settings from the UI

However, this does raise the valid concern of setting visibility from the Strapi admin. We could consider including a read-only view of the settings, as this could help users understand better how their Strapi app is behaving.