-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Dropdown suggestion: allow "value" to be an object #1368
Comments
I've considered this a number of times actually. I'm currently working on improving the allowed values for the The primary reason we've not done this is to date is that we want to preserve the There's a good description of this past issue here: #912 (comment) You can see more historical context here: #754 |
I saw this issue #754 this morning. It's working. thanks. |
I found a not very good but functional solution and the errors stopped :)
values have objects as string, and when send data state for serve i am converter object again
If you have something better I would be happy to know because I believe it is not the ideal solution, although it works, I would like value you can receive an object |
@angelicalleite, I've considered that solution but concluded the one in issue #754 is so much simpler and better, using |
Hi !
|
So I have been using Dropdown for a simple select, except the value can only be a string. Why not allow the value to be an object?
We can access the options via the data object in the onChange function, but then what if we needed the whole single object instead of just its value?
For those knowledgeable about Angular 1.X, it's like the selected item in the ng-options.
The text was updated successfully, but these errors were encountered: