Fix: invoke onPhoneNumberChange callback with formatted value on init instead of unformatted value from previous state #283
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.
Description
When using
formatOnInit
in conjunction withonPhoneNumberChange
, a bug causes the latter callback to be invoked with a value from the not-yet-formatted previous state.This change fixes this behavior and notifies the callback with the updated, formatted value.
I have tried to write two test cases (default and
formatOnInit=false
), but unfortunately, my knowledge of Enzyme is too limited 😥️ The behavior relies on libphonenumber-js-utils to be done loading, so the test cases must run after the deferred are resolved…Types of changes
Checklist: