For most interactive widgets you can define a Minimum and Maximum value, however, a user can still fill out any value and cause it to be sent to the backend.
For example, I define a Numeric with a minimum of 0 and a maximum of 100. However, a user can still type -20 and cause it to be sent to the backend. If your logic relies on the fact that the value is always positive, you'll end up in unpleasant situations. In the toolkit we can cover this by clipping the value received from the UI based on the minimum and maximum properties.
A boolean could be implemented to control this behaviour.
For most interactive widgets you can define a Minimum and Maximum value, however, a user can still fill out any value and cause it to be sent to the backend.
For example, I define a Numeric with a minimum of 0 and a maximum of 100. However, a user can still type -20 and cause it to be sent to the backend. If your logic relies on the fact that the value is always positive, you'll end up in unpleasant situations. In the toolkit we can cover this by clipping the value received from the UI based on the minimum and maximum properties.
A boolean could be implemented to control this behaviour.