Refactor number parsing and validation
Refactor libphonenumber.validateNumber into libphonenumber.parseNumber, which encapsulates the try-catch pattern used in number parsing and returns an object of info about the input number rather tha throwing since we expect to get some invalid number inputs the user is typing. In the conversation model, * Separate phone number validation from search token updating. * Perform token update before save if the number was valid. * Stop storing unneeded number variants as conversation properties. // FREEBIE
This commit is contained in:
parent
7dd0fb70b5
commit
a258f1a66b
6 changed files with 105 additions and 51 deletions
|
@ -22,20 +22,18 @@
|
|||
|
||||
validateNumber: function() {
|
||||
var input = this.$('input.number');
|
||||
try {
|
||||
var regionCode = this.$('li.active').attr('data-country-code').toUpperCase();
|
||||
var number = input.val();
|
||||
|
||||
var parsedNumber = libphonenumber.util.verifyNumber(number, regionCode);
|
||||
var regionCode = this.$('li.active').attr('data-country-code').toUpperCase();
|
||||
var number = input.val();
|
||||
|
||||
var parsedNumber = libphonenumber.util.parseNumber(number, regionCode);
|
||||
if (parsedNumber.isValidNumber) {
|
||||
this.$('.number-container').removeClass('invalid');
|
||||
this.$('.number-container').addClass('valid');
|
||||
return parsedNumber;
|
||||
} catch(e) {
|
||||
return parsedNumber.e164;
|
||||
} else {
|
||||
this.$('.number-container').removeClass('valid');
|
||||
} finally {
|
||||
input.trigger('validation');
|
||||
}
|
||||
input.trigger('validation');
|
||||
}
|
||||
});
|
||||
})();
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue