-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[SelectField] Port component #6301
Conversation
src/SelectField/SelectField.js
Outdated
> | ||
{React.Children.map(children, (child, index) => | ||
React.cloneElement(child, { | ||
selected: value === child.props.value, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also suggest add custom comparator that by default will compare strictly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and use any
prop type for value
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@umidbekkarimov You want to have ability to set custom comparison operator like ==
or ===
, etc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: Filed -> Field
@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