fix: handle v-model.trim
and v-model.number
#2408
Merged
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.
🔎 Overview
This PR handles both
v-model.trim
andv-model.number
modifiers, TheValidationProvider
component uses bothv-model
andinput
event to keep the value tracked, but when one of the two modifiers used, it will end up with 2 different values between re-renders, causing stuff likeeager
mode to break due to it thinking the value changed already in-between the renders.This PR enhances the value normalization, by casting the value to number using
parseFloat
when the number modifier is used. AndString.trim
if the trim modifier is used.✔ Issues affected
closes #2403