-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Allow passing classNames to the input element #598
Comments
+1 |
1 similar comment
+1 |
Somewhat related issue, it looks like if you add |
+1 |
Hello - In an effort to sustain the We understand this might be inconvenient but in the best interest of supporting the broader community we have to direct our efforts towards the current major version. If you aren't using the latest version of However, if you feel this issue is still relevant and you'd like us to review it - please leave a comment and we'll do our best to get back to you! |
+1 |
Greetings all and @POTEAMARDEEP , PR #4625 includes several changes to the input component including the removal of the extra div as well as introducing a new prop to the input component called It is scheduled as a part of the next major release for 5.0 and we should be deploying the beta this week. |
Correct me if I am wrong, but currently you can set the outer element classes via
className
and useoptionRenderer
to add whatever classes you want for the options, but there's currently no way to directly pass classes for the input element.Of course use child selectors and the main
<Select>
classNames, if you absolutely need to, but passingclassNames
to the input element itself would be a nice convenience to have for some situations (such as passing validation classes directly et cetera).The text was updated successfully, but these errors were encountered: