Skip to content

Conversation

@rdjanuar
Copy link
Contributor

@rdjanuar rdjanuar commented Dec 8, 2025

🔗 Linked issue

Resolves #5356

  • 📖 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

When we manually filter the items, the resulting array might be empty ([]). In this situation, the displayed value should be the label, instead of the raw value itself. I am using a cache for props.items and props.modelValue to fix the lookup of the displayedValue

📝 Checklist

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

@github-actions github-actions bot added the v4 #4488 label Dec 8, 2025
@rdjanuar rdjanuar changed the title fix(SelectMenu): wrong displayed value if items not avaiable fix(SelectMenu): wrong displayed value if items not avaiable Dec 8, 2025
@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 8, 2025

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

commit: e718eef

RIzky Djanuar added 3 commits December 8, 2025 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v4 #4488

Projects

None yet

Development

Successfully merging this pull request may close these issues.

USelectMenu: selected items show value instead of label when using custom search/filter logic

1 participant