fix: prevent infinite loop in parsedMode calculation #463
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.
Fix for #462 (and potentially #452)
Issue in version >9 where if prop
mode
set toauto
would be unable to change/edit the phone number input after the phone number has been formatted due to a bug in a compute value ofparsedMode
that leads to an endless changing of value of thephoneObject
which would then change theparsedMode
return value, which would then change the value ofphoneObject
, etc etc.The main culprit of this seems to be of how an
if
condition is being handled makingparsedMode
return the inappropriate value whenresult?.format(toUpperCase(parsedMode.value))
is being executed.