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 cant speak for @hamcher, but I have a case where uniqueness between the objects the select is representing is derived from multiple fields (i.e. composite key). Instead of serializing the fields into one key to use for the value in the MenuItem component, then deserializing it when handling the change event in the onChange handler of the Select component, it would be handy if I could just use the object itself as the key.
A work around for my issue is to add an additional field (immutably or mutably) with the serialized composite key, then to use that serialized key for the value. This isn't ideal when using typescript, but is an ok workaround none the less.
I would say that is better than using an object. It is what you would do if you were to use plain HTML. If you have some kind of identifier for the item, you could use that too.
Duplicates
Latest version
Current behavior 😯
Select support only integer and string value, but i can't use value as object, because some times we need it to use it in a specific case
Expected behavior 🤔
No response
Steps to reproduce 🕹
No response
Context 🔦
No response
Your environment 🌎
No response
The text was updated successfully, but these errors were encountered: