Skip to content
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

Closed
christopherkindl opened this issue Sep 12, 2023 · 9 comments · Fixed by #778 or #789
Closed

[Feature]: <TextArea/> component #670

christopherkindl opened this issue Sep 12, 2023 · 9 comments · Fixed by #778 or #789
Assignees
Labels
Good first issue Beginner-friendly issue for first-time contributors

Comments

@christopherkindl
Copy link
Member

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:

  • placeholder?: string
  • error?: boolean
  • errorMessage?: string
  • disabled?: boolean
  • maxLength?: number

other native props, such as autocomplete, autofocus or required, 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.

_TextArea

@christopherkindl christopherkindl added the Good first issue Beginner-friendly issue for first-time contributors label Sep 12, 2023
@jorgeramirezamora
Copy link

I can take this one @christopherkindl

@christopherkindl
Copy link
Member Author

Thanks so much, @jorgeramirezamora!

@christopherkindl
Copy link
Member Author

Hi @jorgeramirezamora, just wanted to check in whether you still want to tackle this issue? Otherwise happy to re-assign it :)

@jorgeramirezamora
Copy link

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.

@christopherkindl
Copy link
Member Author

@jorgeramirezamora Awesome, thank you!

@Harsh-0986
Copy link

Is this issue resolved?

@lucafaggianelli
Copy link
Contributor

hey @jorgeramirezamora @christopherkindl how's it going with this issue? I'll be happy to work on it if you need help

@severinlandolt severinlandolt mentioned this issue Oct 26, 2023
14 tasks
@severinlandolt severinlandolt linked a pull request Oct 26, 2023 that will close this issue
14 tasks
@github-actions
Copy link

🎉 This issue has been resolved in version 3.11.0-beta.6 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link

github-actions bot commented Nov 6, 2023

🎉 This issue has been resolved in version 3.11.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good first issue Beginner-friendly issue for first-time contributors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants