Input
Input records a single line of text, a number, or a password. It participates in the state, validation, and submission boundary of its Form.
1. When to use it
Typical uses:
- Names, codes, and short titles
- Basic amounts or quantities
- Masked password input
2. Add and configure
- Add Input to the Fields slot of a Form Section.
- Set a stable, unique Field Key / Name that matches the backend DTO property.
- Configure the component properties below, then add Required, Help Text, Full row, or conditions as needed.
- Check the initial value and layout in Design Preview, then use Form Validate / Submit to test the full data path.
3. Main properties
| Property | Purpose |
|---|---|
| Input Type | Sets the initial value, content, or format used by the field. |
| Default Value | Sets the initial value, content, or format used by the field. |
| Hint | Controls how the field is displayed in Design Preview and Runtime. |
| Length Limit | Limits the allowed count, length, or value range. |
| Suffix Unit | Controls how the field is displayed in Design Preview and Runtime. |
| Read Only / Allow Clear | Enables or disables this behavior. |
Common properties such as Field Key, Required, Help Text, Full row, and Visible When come from the Form field contract. The table highlights the settings most relevant to Input.
4. Form value and backend contract
Submitted value: A string for Text / Password, or a number for Number.
"Rocky Yu"
The example shows the data shape only. The API must still validate type, range, and authorization against its business DTO.
5. Validation, conditions, and interactions
Every field can use Form properties such as Required, Visible When, Disabled When, Required When, Dependencies, and Clear When Hidden. Conditions improve interaction but never replace backend validation or authorization.
Component capabilities: Supports onChange, onFocus, and setValue, so value changes can drive later actions.
6. Recommendations
Recommendations: Set explicit length limits for business fields. Never place passwords in defaults, logs, or Page Context.
Return to the Form overview for layout, validation, submission, drafts, and backend protocol guidance.