Skip to content

Comments

feat(InputMenu): add autocomplete prop#6026

Draft
benjamincanac wants to merge 4 commits intov4from
feat/4859
Draft

feat(InputMenu): add autocomplete prop#6026
benjamincanac wants to merge 4 commits intov4from
feat/4859

Conversation

@benjamincanac
Copy link
Member

🔗 Linked issue

Resolves #4859

❓ Type of change

  • 📖 Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Integrate Reka UI's new Autocomplete component into the InputMenu component.

When the autocomplete prop is true, the InputMenu uses Autocomplete.Root and Autocomplete.Input instead of their Combobox counterparts. The modelValue becomes the input text (string) instead of a selected item, turning the component into a free-form text input with optional suggestions.

  • multiple, by, displayValue, resetSearchTermOnSelect and resetModelValueOnClear are not applicable in autocomplete mode.
  • resetSearchTermOnBlur defaults to false in autocomplete mode.
  • Typing updates both the filter and the root's modelValue.

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Feb 11, 2026

npm i https://pkg.pr.new/@nuxt/ui@6026

commit: 6b0babf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

InputMenu behaves like a SelectMenu instead of a true input – needs proper input behavior

1 participant