# Textarea

### Use Cases:

✅ Multi-line input: Use the "Textarea" component when you need users to provide text input that spans multiple lines, such as writing comments, messages, or descriptions.

✅ Formatting and editing: "Textarea" components are suitable for cases where users need to format or edit text, such as composing emails, writing articles, or entering code snippets.

✅ User-generated content: Utilize "Textarea" components for collecting user-generated content, allowing users to share their thoughts, opinions, or creative expressions.

✅ Long-form data entry: "Textarea" components are effective for scenarios requiring users to provide detailed information, such as filling out forms with paragraphs of text.

### Not to Use Cases: 

❌ Single-line input: Avoid using "Textarea" components for single-line input fields, such as names, emails, or short keywords. Instead, use single-line text inputs for such cases.

❌ Excessive space consumption: Do not use "Textarea" components when a single-line text input or other input methods can capture the required information more efficiently and without taking up too much space.

<br>

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://2600hz.gitbook.io/sds/sds-3.0/sds-components/components/textarea.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.