-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
undefined
value for <USelect>
option is not honored, label is used instead
#1702
undefined
value for <USelect>
option is not honored, label is used instead
#1702
Comments
Hey @manniL, Nice to see you around here 😄 This seems to have been implemented on purpose: I hear you though, have the following immediate solution (funcs may not be nessaccry at all):
Guess if important now you can patch in the meantime. Else @benjamincanac what are your thoghts? |
I guess we can remove the default values indeed, I honestly don't remember why we added those 😅 |
I've been looking at this and it doesn't seem related to default values. You need to have an empty @manniL It might be easier to achieve what you want using the |
@benjamincanac still feel that one might have undefined value in array they pass on purpose, surely we should remove the guess functions? |
Environment
Stackblitz
Version
2.15.2
Reproduction
https://stackblitz.com/edit/nuxt-ui-1702?file=package-lock.json
select
is not undefined.Description
When creating options for the
USelect
component and providing a value purposefully asundefined
, the custom value will not be considered and the label value will be used.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: