chore: Go back to isValidNumber vs isValidNumberPrecise. Fixes #50

mpalourdio · Mar 18, 2024 · 37a210e · 37a210e
1 parent e28c75e
commit 37a210e
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,9 +1,13 @@
 # Changelog
 
+## v0.11.1
+
+- Revert: Use `isValidNumber` vs `isValidNumberPrecise`. See this [issue](https://github.com/mpalourdio/intl-tel-input-ng/issues/50).
+
 ## v0.11.0
 
 - `intl-tel-input 19`  support, thanks to [tlebreton](https://github.com/tlebreton).
-- BC: The `onlyLocalized` feature has been removed as it's not needed anymore.
+- BC break: The `onlyLocalized` feature has been removed as it's not needed anymore.
 
 ## v0.10.0
 

diff --git a/src/lib/components/intl-tel-input.component.ts b/src/lib/components/intl-tel-input.component.ts
@@ -55,7 +55,7 @@ export class IntlTelInputComponent implements AfterViewInit {
 
     i18nizePhoneNumber(): void {
         this.E164PhoneNumber = null;
-        if (this._intlTelInput.isValidNumberPrecise()) {
+        if (this._intlTelInput.isValidNumber()) {
             this.E164PhoneNumber = this._intlTelInput.getNumber();
         }
         this.E164PhoneNumberChange.emit(this.E164PhoneNumber);