Open ade10176 opened 2 months ago
I would also like this change for a Maps SDK for JavaScript use case. But I think the issue is more general; the numeric input should enforce the min and max values. Currently, the min/max values only appear to affect the behavior of the buttons.
Check existing issues
Description
Calcite number input currently supports characters like
-
ore
. In a min/max file attachment use case, where-
is not an acceptable entry, user currently can type in-
and is persisted when: • there are no numbers in the input (-
) • following numbers in the input (5-
)if the user enters
5-1
, the-
is omitted, and the entry becomes51
if the user enters
-5
, the entry is not accepted and it triggers a validation errorAcceptance Criteria
Allow configuration to prevent specific character(s) to be entered in the number input. Also welcome to workaround ideas.
Relevant Info
Field Maps Designer issue https://github.com/ArcGIS/field-apps-web/issues/4229
Which Component
calcite input number
Example Use Case
No response
Priority impact
impact - p1 - need for current milestone
Calcite package
Esri team
ArcGIS Field Apps