Handling value parsing exceptions in validation

[vursen]

Describe your motivation

The field components currently set their value to null when the user tries to commit non-parsable input. This causes their validation to fail with the bad input error.

However, there are components where certain user input can be parsed on the client-side but still get rejected by the server due to technical limitations. An example of this is IntegerField, where the user can enter a number that falls within the JavaScript integer limit but exceeds the Java integer limit.

Since such values appear valid to the user, it would make sense to treat them separately from completely nonsensical input (bad input) to allow providing an individual helpful error message instead of an unclear "invalid input".

Describe the solution you'd like

Add a step to the validation that would check if a value parsing exception has been thrown since the last value change. When this is the case, the validation returns an individual error message.

Additional context

Depends on:

• Error messages for constraints #4618

Original requests:

• IntegerField has an incomplete API [1 day] #1035
• Invalid flag goes out of sync when text field is inside custom field #1076 (comment)