This package has been abandoned in favour of odolbeau/phone-number-bundle.
This bundle integrates Google's libphonenumber into your Symfony2-Symfony4 application through the giggsey/libphonenumber-for-php port.
$ composer require misd/phone-number-bundle
// app/AppKernel.php
public function registerBundles()
{
$bundles = array(
// ...
new Misd\PhoneNumberBundle\MisdPhoneNumberBundle()
);
}
The following services are available:
Service | ID | libphonenumber version |
---|---|---|
libphonenumber\PhoneNumberUtil |
libphonenumber.phone_number_util |
|
libphonenumber\geocoding\PhoneNumberOfflineGeocoder |
libphonenumber.phone_number_offline_geocoder |
>=5.8.8 |
libphonenumber\ShortNumberInfo |
libphonenumber.short_number_info |
>=5.8 |
libphonenumber\PhoneNumberToCarrierMapper |
libphonenumber.phone_number_to_carrier_mapper |
>=5.8.8 |
libphonenumber\PhoneNumberToTimeZonesMapper |
libphonenumber.phone_number_to_time_zones_mapper |
>=5.8.8 |
So to parse a string into a libphonenumber\PhoneNumber
object:
$phoneNumber = $container->get('libphonenumber.phone_number_util')->parse($string, PhoneNumberUtil::UNKNOWN_REGION);
Requires doctrine/doctrine-bundle
.
To persist libphonenumber\PhoneNumber
objects, add the Misd\PhoneNumberBundle\Doctrine\DBAL\Types\PhoneNumberType
mapping to your application's config:
// app/config.yml
doctrine:
dbal:
types:
phone_number: Misd\PhoneNumberBundle\Doctrine\DBAL\Types\PhoneNumberType
You can then use the phone_number
mapping:
/**
* @ORM\Column(type="phone_number")
*/
private $phoneNumber;
This creates a varchar(35)
column with a Doctrine mapping comment.
Note that if you're putting the phone_number
type on an already-existing schema the current values must be converted to the libphonenumber\PhoneNumberFormat::E164
format.
The phone_number_format
filter can be used to format a phone number object. A libphonenumber\PhoneNumberFormat
constant can be passed as argument to specify in which format the number should be printed.
For example, to format an object called myPhoneNumber
in the libphonenumber\PhoneNumberFormat::NATIONAL
format:
{{ myPhoneNumber|phone_number_format('NATIONAL') }}
By default phone numbers are formatted in the libphonenumber\PhoneNumberFormat::INTERNATIONAL
format.
The phone_number_of_type
test can be used to check a phone number against a type: A libphonenumber\PhoneNumberType
constant name must be passed to specify to which type a number has to match.
For example, to check if an object called myPhoneNumber
is a libphonenumber\PhoneNumberType::MOBILE
type:
{% if myPhoneNumber is phone_number_of_type('MOBILE') }} %} ... {% endif %}
The format()
method in the phone_number_helper
takes two arguments: a libphonenumber\PhoneNumber
object and an optional libphonenumber\PhoneNumberFormat
constant name or value.
For example, to format $myPhoneNumber
in the libphonenumber\PhoneNumberFormat::NATIONAL
format, either use:
<?php echo $view['phone_number_helper']->format($myPhoneNumber, 'NATIONAL') ?>
or:
<?php echo $view['phone_number_helper']->format($myPhoneNumber, \libphonenumber\PhoneNumberFormat::NATIONAL) ?>
By default phone numbers are formatted in the libphonenumber\PhoneNumberFormat::INTERNATIONAL
format.
The isType()
method in the phone_number_helper
takes two arguments: a libphonenumber\PhoneNumber
object and an optional libphonenumber\PhoneNumberType
constant name or value.
For example, to check if $myPhoneNumberis a
libphonenumber\PhoneNumberType::MOBILE` type:
<?php if $view['phone_number_helper']->isType($myPhoneNumber, 'MOBILE'): ?>
...
<?php endif; ?>
or:
<?php if $view['phone_number_helper']->isType($myPhoneNumber, \libphonenumber\PhoneNumberType::MOBILE): ?>
...
<?php endif; ?>
libphonenumber\PhoneNumber
objectsRequires jms/serializer-bundle
.
Instances of libphonenumber\PhoneNumber
are automatically serialized in the E.164 format.
Phone numbers can be deserialized from an international format by setting the type to libphonenumber\PhoneNumber
. For example:
use JMS\Serializer\Annotation\Type;
/**
* @Type("libphonenumber\PhoneNumber")
*/
private $phoneNumber;
libphonenumber\PhoneNumber
objects in formsYou can use the PhoneNumberType
(phone_number
for Symfony 2.7) form type to create phone number fields. There are two widgets available.
A single text field allows the user to type in the complete phone number. When an international prefix is not entered, the number is assumed to be part of the set default_region
. For example:
use libphonenumber\PhoneNumberFormat;
use Misd\PhoneNumberBundle\Form\Type\PhoneNumberType;
use Symfony\Component\Form\FormBuilderInterface;
public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder->add('phone_number', PhoneNumberType::class, array('default_region' => 'GB', 'format' => PhoneNumberFormat::NATIONAL));
}
By default the default_region
and format
options are PhoneNumberUtil::UNKNOWN_REGION
and PhoneNumberFormat::INTERNATIONAL
respectively.
The phone number can be split into a country choice and phone number text fields. This allows the user to choose the relevant country (from a customisable list) and type in the phone number without international dialling.
use libphonenumber\PhoneNumberFormat;
use Misd\PhoneNumberBundle\Form\Type\PhoneNumberType;
use Symfony\Component\Form\FormBuilderInterface;
public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder->add('phone_number', PhoneNumberType::class, array('widget' => PhoneNumberType::WIDGET_COUNTRY_CHOICE, 'country_choices' => array('GB', 'JE', 'FR', 'US'), 'preferred_country_choices' => array('GB', 'JE')));
}
This produces the preferred choices of 'Jersey' and 'United Kingdom', and regular choices of 'France' and 'United States'.
By default the country_choices
is empty, which means all countries are included, as is preferred_country_choices
.
The option country_placeholder
can be specified to create a placeholder option on above the whole list.
You can use the Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber
constraint to make sure that either a libphonenumber\PhoneNumber
object or a plain string is a valid phone number. For example:
use Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber as AssertPhoneNumber;
/**
* @AssertPhoneNumber
*/
private $phoneNumber;
You can set the default region through the defaultRegion
property:
use Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber as AssertPhoneNumber;
/**
* @AssertPhoneNumber(defaultRegion="GB")
*/
private $phoneNumber;
By default any valid phone number will be accepted. You can restrict the type through the type
property, recognised values:
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::ANY
(default)Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::FIXED_LINE
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::MOBILE
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::PAGER
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::PERSONAL_NUMBER
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::PREMIUM_RATE
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::SHARED_COST
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::TOLL_FREE
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::UAN
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::VOIP
Misd\PhoneNumberBundle\Validator\Constraints\PhoneNumber::VOICEMAIL
(Note that libphonenumber cannot always distinguish between mobile and fixed-line numbers (eg in the USA), in which case it will be accepted.)
/**
* @AssertPhoneNumber(type="mobile")
*/
private $mobilePhoneNumber;
The bundle contains translations for the form field and validation constraints.
In cases where a language uses multiple terms for mobile phones, the generic language locale will use the term 'mobile', while country-specific locales will use the relevant term. So in English, for example, en
uses 'mobile', en_US
uses 'cell' and en_SG
uses 'handphone'.
If your language doesn't yet have translations, feel free to open a pull request to add them in!