fixes #361 - use $event.target.valueAsNumber for number/range inputs,… #363
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #361 - use $event.target.valueAsNumber for number/range inputs, debounce
formatValueToModel
for number/range, removedformatValueToField
Number inputs now support
10e10
formats being typed in, and stores the evaluated value of10e10
(100000000000
) on the model.debounceFormatFunc
for number/range inputs, as well as date/datetime/datetime-localonInput
handler which checks for number/range and uses $event.target.valueAsNumber per @YgamiLightinputType
checks and uses to useinputType.toLowerCase()
, recommend doing this for all fields{}
(just looks cleaner)