NumberInputField component accidentally stringifies its value #1596
By using the event's target value without converting it to a Number object, the value can be stringified, leading to errors when saving it, see Graylog2/graylog2-server#1399
Convert values to Number before propagating the change. Currently only the AlarmCallbackConfiguration dialog is affected, outputs already convert types in the REST API and inputs are still form encoded (thereby having Play correctly translate values).
The text was updated successfully, but these errors were encountered:
On entities using the `ConfigurationForm` component, use `undefined` as value for empty or non-numeric values on a `NumericField`. - Numeric values are still converted into a number, avoiding #1596 - Non-numeric values will raise an error when the browser validates the input - Empty values will be treated as default values in optional input fields, or will raise an error otherwise Fixes #1628