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
[material-ui][Select] Fix variant type #41405
Conversation
Netlify deploy previewhttps://deploy-preview-41405--material-ui.netlify.app/ Bundle size report |
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.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
This looks good @sai6855! #41401 and #41356 are fixed. For #41410, we're missing the error on line 64 of this playground: If we don't fix that one, then I don't know how users will be able to wrap the Select component, which is a common use case. There's another error on line 73 for which I couldn't find a fix, but we can accept that one as a TS limitation. cc: @michaldudak |
636740c
to
f4ccdb4
Compare
@DiegoAndai #41410 is fixed now, i changed implementation by removing I hope i covered all possbile scenarios in tests, but let me know if you see anything missing. Also updated issues in PR description |
Thanks, @sai6855, great work managing all those issues. I think this is the best solution. I agree that the I would like to get @michaldudak's opinion on this before merging. Also, I'll leave a comment at #39137 to see if people involved in that PR have any opinions about this change. |
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.
268d82e
to
fd053d4
Compare
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.
This is the kind of PR that I'm usually quite afraid to approve. It looks OK, I couldn't find anything suspicious, but I can't think of all the ways it will be used in the wild and all the potential ways in can break.
I give a green light based on what I'm able to anticipate currently.
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.
This seems to me as the best step forward as well, given the amount of issues it closes which were created with the initial attempt at improving the variant
type.
Good job @sai6855
closes #41401
closes #41356
closes #41375
closes #41410