# NumberInput

### Use Cases:

✅ Quantity Selection: The Number Input component is commonly used when users need to specify quantities of items, such as selecting the number of products to purchase or the quantity of a specific resource to allocate.

✅ Numeric Parameters: When users need to provide specific numerical parameters or settings, such as selecting a value for a slider, setting a time duration, or specifying numerical constraints for calculations.

✅ Data Input: In data-intensive applications, the Number Input component allows users to input numerical data for analysis, such as entering financial figures, statistical values, or measurements.

✅ Mathematical Operations: When users need to perform calculations or mathematical operations within the application, the Number Input component serves as an input mechanism for mathematical expressions or formulas.

### Not to Use Cases:

❌ Non-Numeric Input: Using the Number Input component for non-numeric input fields, such as text or alphanumeric data. It is important to choose an appropriate input type based on the expected data format.

❌ String Input Validation: Relying solely on the Number Input component to validate or enforce string input formats, such as phone numbers or email addresses. Numeric inputs are designed for numeric data, and using them for non-numeric data can lead to confusion or validation errors.

❌ Critical Password Input: Avoid using the Number Input component for entering sensitive information like passwords. Password inputs require special security considerations, such as obscuring the input and handling the data securely.

❌ Complex Numeric Input Formatting: If the application requires complex numeric input formatting, such as scientific notation or currency symbols, the Number Input component may not be sufficient. In such cases, a custom input or specialized component may be more appropriate.

<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/numberinput.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.