-
Notifications
You must be signed in to change notification settings - Fork 312
fix: add ref support for Web #376
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
fix: add ref support for Web #376
Conversation
|
@Naturalclar gentle bump to review this when you get the time, thanks so much! Fixes issue #375 |
Naturalclar
left a comment
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.
@LucioChavezFuentes thanks for the fix!
|
@LucioChavezFuentes CI seems to be failing could you do me a favor and run the linter on lines you edited? |
|
@Naturalclar I fixed the lint errors. You can review it again. |
|
And thank you for your time to review. |
Naturalclar
left a comment
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.
@LucioChavezFuentes thanks 👍
## [2.3.1](v2.3.0...v2.3.1) (2022-03-01) ### Bug Fixes * add ref support for Web ([#376](#376)) ([c7e4180](c7e4180))
|
🎉 This PR is included in version 2.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
Thank you @Naturalclar, I really appreciate your time on review. |
A few changes on
forwardedRefallows anyone to pass a Reactrefon Web version and get a ref of<select>tag that rendersPicker. I am currently using a forked version with these changes in order to getfocus( )method of<select>tag and avoid dirty code.Let me know guys what do you think. I am fully available to make any changes neccesary.