Bug: parsePhoneNumber omits countryCode when it wouldn't have to

[Lemonexe]

Version 5.10.0

Description

I have noticed cases of unexpected behaviour of parsePhoneNumber, where it successfully detects a country calling code, as evidenced by the fact that it returns regionCode, the two-letter ISO country code, but it does not return a countryCode, the calling code itself, as it normally would.

It happens when the input is just the calling code, and between 0 to 2 numbers.

The countryCode can be mapped from regionCode by using getCountryCodeForRegionCode, so it is not a dealbreaker, just an inconvenience.

Steps to reproduce

Returns both properties: ✅

const { countryCode, regionCode } = parsePhoneNumber('+1555444333')
countryCode -> 1, regionCode -> 'US'

Does not return countryCode ❌ :

const { countryCode, regionCode } = parsePhoneNumber('+1')
countryCode -> undefined, regionCode -> 'US'

[grantila]

"+1" is not a valid phone number, it finding the region code is more of an interesting coincidence than something technically supported. The code internally only does a reverse lookup once a real phone number is found (because it might actually not be US just because it starts with "+1").

Use the getRegionCodeForCountryCode if you want to convert +1 to US and getCountryCodeForRegionCode for the other way around.