You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the reproduction link and try changing Select value to "Pineapple" twice.
You can see that first time it's numeric, then it's string.
Describe the bug
You can see that when selecting any option that has a numeric value - there's an issue - no label is shown as the emitted value doesn't match any of the values from the option because it is transformed to a string, because SelectRoot emits a string value from the select HTML element and this breaks a lot of scenarios.
Also, for example in our app, we don't need the native select, input[type=checkbox] etc. elements, as they break our integration with vee-validate by emitting redundant events. @zernonia do you think it makes sense to allow configuring whether a native element is needed at all? Anyway, for now the solution would probably be to just fix this here.
Expected behavior
It should not emit a string value or any value whatsoever.
Context & Screenshots (if applicable)
No response
The text was updated successfully, but these errors were encountered:
Environment
Link to minimal reproduction
https://stackblitz.com/edit/q8eqei5r?file=src%2FApp.vue
Steps to reproduce
Use the reproduction link and try changing
Select
value to "Pineapple" twice.You can see that first time it's numeric, then it's string.
Describe the bug
You can see that when selecting any option that has a numeric value - there's an issue - no label is shown as the emitted value doesn't match any of the values from the option because it is transformed to a string, because
SelectRoot
emits a string value from theselect
HTML element and this breaks a lot of scenarios.Also, for example in our app, we don't need the native
select
,input[type=checkbox]
etc. elements, as they break our integration with vee-validate by emitting redundant events.@zernonia do you think it makes sense to allow configuring whether a native element is needed at all? Anyway, for now the solution would probably be to just fix this here.
Expected behavior
It should not emit a string value or any value whatsoever.
Context & Screenshots (if applicable)
No response
The text was updated successfully, but these errors were encountered: