-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
[Autocomplete] Add closeIcon and popupIcon props #18266
[Autocomplete] Add closeIcon and popupIcon props #18266
Conversation
Details of bundle changes.Comparing: ba1f645...6418141
|
@oliviertassinari what I meant is to change the icon with leaving the |
What about a |
So I think they will be like this
|
Ok, my bad, my proposal wouldn't work. What do you think of not solving this problem, but instead, to use the |
But I think what I've done is better for it in this case |
Here's a review of icon override props (doesn't include any props that set the default icon): Checkbox: Chip: ExpansionPanelSummary: NativeSelect: Radio: Select: StepLabel: Switch: TableSortLabel: It's a bit of a mish-mash for both prop-naming and descriptions, so could do with being reconciled, but for the purpose of this PR, only 3 have For autocomplete, how about we use For the description, "The icon to display in place of the default XXX icon."? (Whatever wording is chosen needs to work for the other components.) |
@mbrookes I think that the idea case is to accept an element. However, it's not always possible, in the case of the select, it accepts a component instead to avoid the cloneElement API. I think that there is a tradeoff to find here between allowing to customize the icon, the icon button and more. I'm wondering about the best tradeoff we can pick. Here are the different options:
I think that I would prefer the options in this order 4, 1, 3, 2. Now, 1 and 4 can probably be used in conjunction, no strong preference. |
63ea9b8
to
6418141
Compare
@AbdallahElroby Thanks |
@oliviertassinari you're welcome |
Closes #18227