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
The Select component takes a Model<Option<T>> for the value. But this over complicates things in most cases, since there select would never have a None option. So the user needs to .unwrap() or match on the value every time they need to access it.
If the Option is removed, and user does in fact need a None option for their select, then they can make their own value be Option<T>, whilst the Select component itself doesn't need to care if the value uses an Option or not.
If you're happy with this change, I can implement it in #166
The text was updated successfully, but these errors were encountered:
The Select component takes a
Model<Option<T>>
for the value. But this over complicates things in most cases, since there select would never have aNone
option. So the user needs to.unwrap()
or match on the value every time they need to access it.If the
Option
is removed, and user does in fact need aNone
option for their select, then they can make their own value beOption<T>
, whilst theSelect
component itself doesn't need to care if the value uses an Option or not.If you're happy with this change, I can implement it in #166
The text was updated successfully, but these errors were encountered: