forms: provide the the min/max value in validator error messages

[michael-smt]

Prerequisites

• I have read the Contributing Guidelines.
• I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

Feature request

For the the min* and max* validators, the validator error messages from the SiFormValidationErrorMapper should include information about what the smallest or biggest accepted value is.

For example instead of The value is too small the message could be The value should be {{min}} or more.

Affected error messages and translation keys:

• min / SI_FORM_CONTAINER.ERROR.MIN
• max / SI_FORM_CONTAINER.ERROR.MAX
• minlength / SI_FORM_CONTAINER.ERROR.MIN_LENGTH
• maxlength / SI_FORM_CONTAINER.ERROR.MAX_LENGTH
• minDate / SI_FORM_CONTAINER.ERROR.MIN_DATE
• maxDate / SI_FORM_CONTAINER.ERROR.MAX_DATE
• minTime / SI_FORM_CONTAINER.ERROR.MIN_TIME
• maxTime / SI_FORM_CONTAINER.ERROR.MAX_TIME

Use case

The user sees what values are expected.

[michael-smt]

Suggested texts from UX writer @Danisand:

• min: Min. {{limit}}
• max: Max. {{limit}}
• minlength: Min. {{limit}} characters
• maxlength: Max. {{limit}} characters
• minDate: Date after {{date}} required
• maxDate: Date prior to {{date}} required

These have no suggestion yet, @Danisand can you please add them

• minTime / SI_FORM_CONTAINER.ERROR.MIN_TIME
• maxTime / SI_FORM_CONTAINER.ERROR.MAX_TIME

[Danisand]

Hi @michael-smt

Here are my proposals:

• minTime : Time after {{time}} required
• maxTime : Time prior to {{time}} required

[spliffone]

@Danisand A general question, shall error messages are written as sentence and end with a dot? While looking into the code I realize we have multiple ways writing a the messages e.g. The value is not a valid number. or The minutes are not valid.. Secondly is it necessary to use Min. ... why do we shorten the text.

[michael-smt]

Regarding the formatting, @Danisand gave the following input:

• {{date}} should be shown in a localized short format (e.g. 26.01.2026)
• {{time}} should be shown in a localized format in either
  • in hours and minutes when seconds and milliseconds are zero
  • in hours and minutes and seconds when milliseconds are zero
  • in hours and minutes and seconds and milliseconds when all values are present

[Danisand]

@Danisand A general question, shall error messages are written as sentence and end with a dot? While looking into the code I realize we have multiple ways writing a the messages e.g. The value is not a valid number. or The minutes are not valid.. Secondly is it necessary to use Min. ... why do we shorten the text.

We are using the telegram style to follow the Nobody came here to read paradigm:

• The value is not a valid number. ==> Integer required
• The minutes are not valid. ==> Integer between 0 and 59 required
• About min: This is a common practice, which we do since several years. See i18n.

@spliffone In general, I see several strings in the Element design system which I would like to change. Therefore we are performing an UX writing review within the language pack.

[spliffone]

@Danisand Please, have a look to the referenced PR, just. a few things:

• instead of Integer required -> Number required since the input accept both float and integer numbers
• the adjustments to the data messages we need to discuss, without an explicit formatter the default string representation of a date would be displayed. We need to discuss what are the best options to adjust the date format.

@siemens/siemens-element Do you have any ideas how we should provide the min/max date in a error message? Simply passing the Date object would result in the default string representation below. But the only thing which comes to my mind is to provide an extra error param like minString were we internal format the data according to the configuration.