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
I think this would mainly affect v-radiov-toggle and v-checkbox. Though it could also be applied to v-select components.
Off the top of my head I can't think of a good example use case. This may mean it is more of an edge case, but because these aren't actual html elements there is no technical limitation to passing around objects instead of just strings.
So, unless someone can come up with unintended side effect then it seems like it would be a useful feature if a developer needs it. Especially since this isn't something that takes extra code to implement it would just involve changing the allowed types for value properties.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord
lockbot
locked as resolved and limited conversation to collaborators
Apr 15, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think this would mainly affect
v-radio
v-toggle
andv-checkbox
. Though it could also be applied tov-select
components.Off the top of my head I can't think of a good example use case. This may mean it is more of an edge case, but because these aren't actual html elements there is no technical limitation to passing around objects instead of just strings.
So, unless someone can come up with unintended side effect then it seems like it would be a useful feature if a developer needs it. Especially since this isn't something that takes extra code to implement it would just involve changing the allowed types for value properties.
The text was updated successfully, but these errors were encountered: