There appears to be a bug with w-autocomplete that currently restricts it to working with numbers as the item value. The modelValue is typed as String, Number, Array so I'm assuming it was intended to work with strings too. The modelValue values were being converted to a number during the item list comparison, which meant it would never find the string values due to the strict comparison.
There appears to be a bug with w-autocomplete that currently restricts it to working with numbers as the item value. The modelValue is typed as
String, Number, Arrayso I'm assuming it was intended to work with strings too. The modelValue values were being converted to a number during the item list comparison, which meant it would never find the string values due to the strict comparison.