Autocomplete field

[Paul-Bob]

Avo already provides some solutions for autocomplete fields. The goal of this discussion is to take the best ideas from each and build a proper autocomplete field.

The Tags field with fetch values has been a great solution, but it lacks customization at the list item level.

The Belongs To field with the searchable option allows item customization, but it only supports selecting one result and is tied to a record, association, and resource.

The autocomplete field shouldn’t be tied to a record or resource. The DSL and data source are still to be discussed and decided, but here are some key points it should follow:

• Work anywhere (for example, in actions) without record/resource-backed logic
• Option to customize each item component in the results list
• Option to configure the data source (endpoint for example)
• Maybe: Option to select more than one item (configurable)

---

This request has been recurring, so to keep everything centralized, I’m adding here a list of issues where this topic has been discussed in some way. I’m also closing any issues that don’t have remaining tasks, except those related to the autocomplete field.

• Add a proper autocomplete field #2150
• Avo actions: belongs_to on INDEX level breaks #3848

Something to keep in mind is that we also want an autocomplete solution for filters. I’m not saying it should use the same field or components, but it’s something to discuss and consider.

Filters-related issues:

• Implement dynamic filters autocomplete field #2980
• Fuzzy-search for dropdowns #2631