> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/1-wprowadzanie-danych-inputs/obszar-tekstu-textarea.md).
# Text area - TextArea
Multi-line text input field.
✅ **When to use:**
* The entered data consists of several sentences or a longer description (e.g., an opinion, justification).
:x: **When not to use:**
* The data fits on one line. **Use**: [TextField](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/1-wprowadzanie-danych-inputs/pole-tekstowe-textfield.md).
## Component properties
| Eximee Designer property | Attribute name in Source | Description |
| ------------------------------------------------------------------------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Character counter** (section **Data quality**) | characterCounter | If set to "true", a counter showing how many characters have been entered will be displayed under the component. If, additionally, the field has a value set in the field **Maximum number of characters**, the component will also display information about the possible maximum number of characters that can be entered. Showing validation errors hides the counter. The availability of this feature depends on the license and may not be available in all deployments. |
| **Maximum number of characters** | maxLength | Maximum number of characters possible to enter in the field |
| **Message for exceeding the maximum number of characters** (section **Data quality**) | maxLengthWarning | Message displayed after exceeding **the maximum number of characters** |
| **Maximum number of lines** (section **Data quality**) | maxLines | Maximum number of lines |
| **Minimum number of characters** (section **Data quality**) | minLength | Minimum number of characters |
| **Height of the text area (px)** (section **Data quality**) | inputHeight |
Allows changing the height of the text area (in pixels). The default height of the component is 75px. The component does not automatically increase its height after entering more text - once the available space is exceeded, a scrollbar appears on the right side of the field, allowing you to browse the content.
The availability of this feature depends on the license and may not be available in all deployments.
|
{% hint style="warning" %}
Due to its purpose and the possibility of entering a larger body of text, the text area component does not have automatic content formatting functionality.
{% endhint %}
> More information about component properties: [Common component properties](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/wspolne-wlasciwosci-komponentow.md)
Figure 1. Appearance of the component on the request with a specified maximum and minimum number of characters.
Figure 2. Appearance of the inactive component on the request.
{% hint style="info" %}
Demo request: demoKomponentyTekstowe and demoTekstowe
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/1-wprowadzanie-danych-inputs/obszar-tekstu-textarea.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
