Download the PHP package propaganistas/laravel-phone without Composer
On this page you can find all versions of the php package propaganistas/laravel-phone. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
All versions of laravel-phone with dependencies
Informations about the package laravel-phone
Table of Contents
- Attribute casting
- Utility class
- Number information
- Helper function
- Database considerations
Check out the behavior of this package in the demo.
Run the following command to install the latest applicable version of the package:
The Service Provider gets discovered automatically by Laravel.
In your languages directory, add an extra translation in every
validation.php language file:
To validate a phone number, use the
phone keyword in your validation rules array or use the
Phone rule class to define the rule in an expressive way. The phone validator is able to operate in three ways.
You either specify ISO 3166-1 alpha-2 compliant country codes yourself as parameters for the validator, e.g.:
The validator will check if the number is valid in at least one of provided countries, so feel free to add as many country codes as you like.
You provide a dedicated country input field (keyed by ISO 3166-1 compliant country codes) to allow end users to supply a country on their own. Make sure the country field has the same name as the phone field but with _country appended for automatic discovery, or provide your custom country field name as a parameter to the validator:
You instruct the validator to detect which country the number belongs to using the
AUTOkeyword (and optionally any fallback countries):
The validator will try to extract the country from the number itself and then check if the number is valid for that country. If the country could not be guessed it will be validated using the fallback countries if provided. Note that country guessing will only work when phone numbers are entered in international format (prefixed with a
+sign, e.g. +32 ....). Leading double zeros will NOT be parsed correctly as this isn't an established consistency.
To specify constraints on the number type, just append the allowed types to the end of the parameters, e.g.:
The most common types are
fixed_line, but feel free to use any of the types defined here.
You can also enable more lenient validation (for example, fixed lines without area codes) by using the
LENIENT parameter. This feature inherently doesn't play well with country autodetection and number type validation, so use such combo at own risk.
Two cast classes are provided for automatic casting of Eloquent model attributes:
Both classes automatically cast the database value to a PhoneNumber object for further use in your application.
When setting a value, they both accept a string value or a PhoneNumber object.
RawPhoneNumberCast mutates the database value to the raw input number, while the
E164PhoneNumberCast writes a formatted E.164 phone number to the database.
In case of
RawPhoneNumberCast, the cast needs to be hinted about the phone country in order to properly parse the raw number into a phone object.
In case of
E164PhoneNumberCast and the value to be set is not already in some international format, the cast needs to be hinted about the phone country in order to properly mutate the value.
Both classes accept cast parameters in the same way:
- When a similar named attribute exists, but suffixed with
_country(e.g. phone_country), the cast will detect and use it automatically.
- Provide another attribute's name as a cast parameter
- Provide one or several country codes as cast parameters
In order to not encounter any unexpected issues when using these casts, please always validate any input using the validation rules previously described.
⚠️ Attribute assignment and
Due to the nature of
E164PhoneNumberCast a valid country attribute is expected if the number is not passed in international format. Since casts are applied in the order of the given values, be sure to set the country attribute before setting the phone number attribute. Otherwise
E164PhoneNumberCast will encounter an empty country value and throw an unexpected exception.
Utility PhoneNumber class
A phone number can be wrapped in the
Propaganistas\LaravelPhone\PhoneNumber class to enhance it with useful utility methods. It's safe to directly reference these objects in views or when saving to the database as they will degrade gracefully to the E.164 format.
A PhoneNumber can be formatted in various ways:
Get some information about the phone number:
The package exposes the
phone() helper function that returns a
Propaganistas\LaravelPhone\PhoneNumber instance or the formatted string if
$format was provided:
Disclaimer: Phone number handling is quite different in each application. The topics mentioned below are therefore meant as a set of thought starters; support will not be provided.
Storing phone numbers in a database has always been a speculative topic and there's simply no silver bullet. It all depends on your application's requirements. Here are some things to take into account, along with an implementation suggestion. Your ideal database setup will probably be a combination of some of the pointers detailed below.
The E.164 format globally and uniquely identifies a phone number across the world. It also inherently implies a specific country and can be supplied as-is to the
- One column to store the phone number
- To format the phone number to E.164 before persisting it
- User input =
- Database column
Presenting the phone number the way it was inputted
If you store formatted phone numbers the raw user input will unretrievably get lost. It may be beneficial to present your users with their very own inputted phone number, for example in terms of improved user experience.
- Two columns to store the raw input and the correlated country
- User input =
- Database columns
Searching through phone numbers can quickly become ridiculously complex and will always require deep understanding of the context and extent of your application. Here's a possible approach covering quite a lot of "natural" use cases.
- Three additional columns to store searchable variants of the phone number:
- Normalized input (raw input with all non-alpha characters stripped)
- National formatted phone number (with all non-alpha characters stripped)
- E.164 formatted phone number
- Probably a
saving()observer (or equivalent) to prefill the variants before persistence
- An extensive search query utilizing the searchable variants
- User input =
- Database columns
- Search query: