-
Notifications
You must be signed in to change notification settings - Fork 469
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
[Feature]: <TextArea/> component #670
Comments
I can take this one @christopherkindl |
Thanks so much, @jorgeramirezamora! |
Hi @jorgeramirezamora, just wanted to check in whether you still want to tackle this issue? Otherwise happy to re-assign it :) |
Hey @christopherkindl, yeah sorry. I hope to finish by THE end of this week. |
@jorgeramirezamora Awesome, thank you! |
Is this issue resolved? |
hey @jorgeramirezamora @christopherkindl how's it going with this issue? I'll be happy to work on it if you need help |
🎉 This issue has been resolved in version 3.11.0-beta.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.11.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What problem does this feature solve?
<TextArea/>
has been requested by a lot of users. Tremor team is also reworking their entire block section where they find a need for this component.What does the proposed API look like?
Please use HTML's native <textarea/> component. Styling same as in other input elemens, such as
<TextInput/>
.Explicit props:
other native props, such as
autocomplete
,autofocus
orrequired
, should be passed via...other
(see<TextInput/>
).Please comment below if you want to work on this issue and we will assign you. Many thanks for your contribution in advance.
The text was updated successfully, but these errors were encountered: