Description
On config input fields (especially numeric ones), there is no validation of values. For example, it's possible to enter 0 or negative values for settings where this should not be possible as it does not make sense.
Ideally, there is a validation for each input field which defines what the boundaries are (e.g. min/max on a numeric field or length on a string field). This could be done by having a specific validation on the server side which reports an invalid value in case the frontend sends an invalid value, or if needed that the frontend gets the information as well, so it can verify even before sending.
Description
On config input fields (especially numeric ones), there is no validation of values. For example, it's possible to enter 0 or negative values for settings where this should not be possible as it does not make sense.
Ideally, there is a validation for each input field which defines what the boundaries are (e.g. min/max on a numeric field or length on a string field). This could be done by having a specific validation on the server side which reports an invalid value in case the frontend sends an invalid value, or if needed that the frontend gets the information as well, so it can verify even before sending.