[SelectField] Port component#6301
Conversation
| > | ||
| {React.Children.map(children, (child, index) => | ||
| React.cloneElement(child, { | ||
| selected: value === child.props.value, |
There was a problem hiding this comment.
I also suggest add custom comparator that by default will compare strictly
There was a problem hiding this comment.
and use any prop type for value
There was a problem hiding this comment.
@umidbekkarimov You want to have ability to set custom comparison operator like == or ===, etc?
There was a problem hiding this comment.
There was a problem hiding this comment.
Mostly deepEqual, I use { id, name } objects across my project alot, and pass them as a value prop to SelectField.
There was a problem hiding this comment.
It worth discussion, cause previous API supported this http://www.material-ui.com/#/components/select-field
And it would be another breaking change.
Anyways it's easy to write wrapper over it.
There was a problem hiding this comment.
@umidbekkarimov You are right, fixed both 😄
|
@nathanmarks Might have already started migrating the select component. What's the status on that? |
|
@oliviertassinari any updates? |
| @@ -0,0 +1,10 @@ | |||
| # Select Filed | |||
|
@kybarg I'm hoping that @nathanmarks could bring us some light 💡 . He made quite some progress with the component but he lost his work by mistake. |
|
In case that might help, I have been cleaning the issues for the SelectField component. Here is the list That's a challenging component to port to I have been trying the component out locally, here is the first issue I noticed: |
|
Is anyone actively working on this? I've been hacking on the work done here and I'm wondering if using an actual I've been looking at the way Angular-Material (original and v2) build their select component and they're using "divs" in a similar way to MUI's master branch impl. From what I can tell, using a |
|
Oh, I see in the first post that we want the |
|
@dummerbd Sorry, switched to work on |
|
I'm adding the on hold state to this PR as @dummerbd is continuing the effort 😄 . |
|
I don't think that we need to keep this PR opened. I'm closing. |

This is PR is just to start discussion on #5716 and #4792 as for now
Desired functionality:
<select>element as base to handle autofillOverall progress