I have the requirement to manage large no.s of phone number ranges.

This PR includes a new class PhoneNumberRange which can store a contiguous range of phone numbers.

New operators have been added to the PhoneNumber class to facilitate implementation of a ranges and numeric comparison of phone numbers.

Small improvements to the description of exceptions to make locating the data that caused the problem easier.

Added unit tests for PhoneNumberRange and the new operators in PhoneNumber.

All unit tests are passing.

there is no 'general' type in PhoneNumberType.So I can't use validate method with general type.The 'type = null' behavior is add all PhoneNumberType related pattern to patterns list for pattern matching. For number that only hit general pattern will return false by validate method.

I wonder if it is possible to use this library to reverse its purpose i.e. to format a set of numbers into a phone number for a. given country:

1234567890 -> (US) -> 123-456-7890

Hello 👋🏻

In this PR you will find the following: ✅

• Removed a redundant code line that was breaking the documentation format in pub.dev
• Added a notice for the breaking changes in version 7.0.0
• Enhanced the indentation of the code snippets

I hope you like it.

Thanks ❤ Moaz El-sawaf

The addition of the two parameters to fromRaw seems to be a more logical API. I've deprecated the other constructors as of now, before removing those in the future.

steps required to remove others:

• migrate tests
• remove unnecessary methods and factories on phoneNumber and parser

Hello, Can you add formatting option to international format.

I'm writing TextInputFormatter class for this librarry. Need to output national and international format

Thanks in advance

Hi,

if I try to convert a US international call number to E164 using fromIso the country code is in my opinion not checked correctly in PhoneParser: Expected: PhoneNumber.fromIsoCode(IsoCode.US,"01149301234567").international == "+49301234567" Result: "+101149301234567" In contrast to the comment in line 74 phone_parser.dart the check does not check if any country code followed the international prefix but only checks if the given IsoCode prefix followed. ("if a country code did not immediately follow the international prefix") (E.g. parsing any non-german number with fromIsoCode(IsoCode.DE,"00....") also does not work).

Or maybe I used the wrong function, but I would assume if I have a "national" international number I need to parse it with PhoneNumber.fromIsoCode, specififying the originating country?

Cheers, Martin

Since 5.0.0, instead of specifying a country ISO code as string, this library requires using the generated enum. This is fine when a country is known at compilation time, but for multi-national apps it breaks the workflow. All I know is a string. Even if it were a enum, it would be a different enum, coming from a different library.

Is there a way to use string ISO codes with this library?

Hi, I noticed that a test number I have +44 7000000002 works in libphonenumber, but not with this library.

I am not sure why, because it seems that you use libphonenumbers metadata...

This library is great and imo superior to the other phone number libs out there. However, I can't figure out how to implement proper on-the-fly formatting with Flutter's TextInputFormatter.

I tried to reference the TextInputFormatter from https://github.com/bottlepay/flutter_libphonenumber/blob/master/lib/src/input_formatter/input_formatter.dart

however, this library's formatting doesn't really seem to work with phone numbers while they are being typed and still incomplete.

Hi The static function PhoneNumber.fromRaw throw an exeception with a valid E164 phone number

PhoneNumber.fromRaw('+33655570500')

PhoneNumberException (PhoneNumberException(code: Code.invalidCountryCallingCode, description: countryCode 3 not found))

When trying to format incomplete numbers for "as-you-type" formatting, some countries produce wrong numbers by adding excess leading number at some stage. I were able to reproduce it only for countries with existing nationalPrefixTransformRule in metadata.

Code to reproduce

import 'package:phone_numbers_parser/phone_numbers_parser.dart';

void main() {
  final fullBermudaNumber = PhoneNumber.parse('+14412957070');
  final incompleteBermudaNumber = PhoneNumber.parse('+14412957');

  print(fullBermudaNumber.nsn); // 4412957070 OK
  print(fullBermudaNumber.getFormattedNsn()); // 4412957070 OK

  print(incompleteBermudaNumber.nsn); // 4414412957 WRONG (4412957 expected)
  print(incompleteBermudaNumber.getFormattedNsn()); // 4414412957 WRONG (4412957 expected)

  final fullUSNumber = PhoneNumber.parse('+14056343023');
  final incompleteUSNumber = PhoneNumber.parse('+14056343');

  print(fullUSNumber.nsn); // 4056343023 OK
  print(fullUSNumber.getFormattedNsn()); // 405-634-3023 OK

  print(incompleteUSNumber.nsn); // OK
  print(incompleteUSNumber.getFormattedNsn()); // 405-634-3 OK
}