PHP Standalone Validation Library
PHP Standalone library for validating data. Inspired by Illuminate\Validation Laravel.
$_FILES validation with multiple file support.composer require "rakit/validation"
There are two ways to validating data with this library. Using make to make validation object,
then validate it using validate. Or just use validate.
Examples:
Using make:
…
or just validate it:
…
In this case, 2 examples above will output the same results.
But with make you can setup something like custom invalid message, custom attribute alias, etc before validation running.
By default we will transform your attribute into more readable text. For example confirm_password will be displayed as Confirm password.
But you can set it anything you want with setAlias or setAliases method.
Example:
$validator = new Validator;
// To set attribute alias, you should use `make` instead `validate`.
$validation->make([
'province_id' => $_POST['province_id'],
'district_id' => $_POST['district_id']
], [
'province_id' => 'required|numeric',
'district_id' => 'required|numeric'
]);
// now you can set aliases using this way:
$validation->setAlias('province_id', 'Province');
$validation->setAlias('district_id', 'District');
// or this way:
$validation->setAliases([
'province_id' => 'Province',
'district_id' => 'District'
]);
// then validate it
$validation->validate();
Now if province_id value is empty, error message would be 'Province is required'.
Before register/set custom messages, here are some variables you can use in your custom messages:
:attribute: will replaced into attribute alias.:value: will replaced into stringify value of attribute. For array and object will replaced to json.And also there are several message variables depends on their rules.
Here are some ways to register/set your custom message(s):
With this way, anytime you make validation using make or validate it will set your custom messages for it.
It is useful for localization.
To do this, you can set custom messages as first argument constructor like this:
$validator = new Validator([
'required' => ':attribute harus diisi',
'email' => ':email tidak valid',
// etc
]);
// then validation belows will use those custom messages
$validation_a = $validator->validate($dataset_a, $rules_for_a);
$validation_b = $validator->validate($dataset_b, $rules_for_b);
Or using setMessages method like this:
$validator = new Validator;
$validator->setMessages([
'required' => ':attribute harus diisi',
'email' => ':email tidak valid',
// etc
]);
// now validation belows will use those custom messages
$validation_a = $validator->validate($dataset_a, $rules_for_dataset_a);
$validation_b = $validator->validate($dataset_b, $rules_for_dataset_b);
Sometimes you may want to set custom messages for specific validation.
To do this you can set your custom messages as 3rd argument of $validator->make or $validator->validate like this:
$validator = new Validator;
$validation_a = $validator->validate($dataset_a, $rules_for_dataset_a, [
'required' => ':attribute harus diisi',
'email' => ':email tidak valid',
// etc
]);
Or you can use $validation->setMessages like this:
$validator = new Validator;
$validation_a = $validator->make($dataset_a, $rules_for_dataset_a);
$validation_a->setMessages([
'required' => ':attribute harus diisi',
'email' => ':email tidak valid',
// etc
]);
...
$validation_a->validate();
Sometimes you may want to set custom message for specific rule attribute.
To do this you can use : as message separator or using chaining methods.
Examples:
$validator = new Validator;
$validation_a = $validator->make($dataset_a, [
'age' => 'required|min:18'
]);
$validation_a->setMessages([
'age:min' => '18+ only',
]);
$validation_a->validate();
Or using chaining methods:
$validator = new Validator;
$validation_a = $validator->make($dataset_a, [
'photo' => [
'required',
$validator('uploaded_file')->fileTypes('jpeg|png')->message('Photo must be jpeg/png image')
]
]);
$validation_a->validate();
Translation is different with custom messages.
Translation may needed when you use custom message for rule in, not_in, mimes, and uploaded_file.
For example if you use rule in:1,2,3 we will set invalid message like "The Attribute only allows '1', '2', or '3'"
where part "'1', '2', or '3'" is comes from ":allowed_values" tag.
So if you have custom Indonesian message ":attribute hanya memperbolehkan :allowed_values",
we will set invalid message like "Attribute hanya memperbolehkan '1', '2', or '3'" which is the "or" word is not part of Indonesian language.
So, to solve this problem, we can use translation like this:
// Set translation for words 'and' and 'or'.
$validator->setTranslations([
'and' => 'dan',
'or' => 'atau'
]);
// Set custom message for 'in' rule
$validator->setMessage('in', ":attribute hanya memperbolehkan :allowed_values");
// Validate
$validation = $validator->validate($inputs, [
'nomor' => 'in:1,2,3'
]);
$message = $validation->errors()->first('nomor'); // "Nomor hanya memperbolehkan '1', '2', atau '3'"
Actually, our built-in rules only use words 'and' and 'or' that you may need to translates.
Errors messages are collected in Rakit\Validation\ErrorBag object that you can get it using errors() method.
$validation = $validator->validate($inputs, $rules);
$errors = $validation->errors(); // all();
// [
// 'Email is not valid email',
// 'Password minimum 6 character',
// 'Password must contains capital letters'
// ]
$messages = $errors->all('
:message
');
// [
// '
Email is not valid email
',
// '
Password minimum 6 character
',
// '
Password must contains capital letters
'
// ]
firstOfAll(string $format = ':message', bool $dotNotation = false)Get only first message from all existing keys.
Examples:
$messages = $errors->firstOfAll();
// [
// 'email' => Email is not valid email',
// 'password' => 'Password minimum 6 character',
// ]
$messages = $errors->firstOfAll('
:message
');
// [
// 'email' => '
Email is not valid email
',
// 'password' => '
Password minimum 6 character
',
// ]
Argument $dotNotation is for array validation.
If it is false it will return original array structure, if it true it will return flatten array with dot notation keys.
For example:
$messages = $errors->firstOfAll(':message', false);
// [
// 'contacts' => [
// 1 => [
// 'email' => 'Email is not valid email',
// 'phone' => 'Phone is not valid phone number'
// ],
// ],
// ]
$messages = $errors->firstOfAll(':message', true);
// [
// 'contacts.1.email' => 'Email is not valid email',
// 'contacts.1.phone' => 'Email is not valid phone number',
// ]
first(string $key)Get first message from given key. It will return string if key has any error message, or null if key has no errors.
For example:
if ($emailError = $errors->first('email')) {
echo $emailError;
}
toArray()Get all messages grouped by it's keys.
For example:
$messages = $errors->toArray();
// [
// 'email' => [
// 'Email is not valid email'
// ],
// 'password' => [
// 'Password minimum 6 character',
// 'Password must contains capital letters'
// ]
// ]
count()Get count messages.
has(string $key)Check if given key has an error. It returns bool if a key has an error, and otherwise.
For example you have validation like this:
$validation = $validator->validate([
'title' => 'Lorem Ipsum',
'body' => 'Lorem ipsum dolor sit amet ...',
'published' => null,
'something' => '-invalid-'
], [
'title' => 'required',
'body' => 'required',
'published' => 'default:1|required|in:0,1',
'something' => 'required|numeric'
]);
You can get validated data, valid data, or invalid data using methods in example below:
$validatedData = $validation->getValidatedData();
// [
// 'title' => 'Lorem Ipsum',
// 'body' => 'Lorem ipsum dolor sit amet ...',
// 'published' => '1' // notice this
// 'something' => '-invalid-'
// ]
$validData = $validation->getValidData();
// [
// 'title' => 'Lorem Ipsum',
// 'body' => 'Lorem ipsum dolor sit amet ...',
// 'published' => '1'
// ]
$invalidData = $validation->getInvalidData();
// [
// 'something' => '-invalid-'
// ]
Click to show details.
required
The field under this validation must be present and not 'empty'.
Here are some examples:
| Value | Valid |
|---|---|
'something' |
true |
'0' |
true |
0 |
true |
[0] |
true |
[null] |
true |
| null | false |
| [] | false |
| '' | false |
For uploaded file, $_FILES['key']['error'] must not UPLOAD_ERR_NO_FILE.
required_if:another_field,value_1,value_2,...
The field under this rule must be present and not empty if the anotherfield field is equal to any value.
For example required_if:something,1,yes,on will be required if something value is one of 1, '1', 'yes', or 'on'.
required_unless:another_field,value_1,value_2,...
The field under validation must be present and not empty unless the anotherfield field is equal to any value.
required_with:field_1,field_2,...
The field under validation must be present and not empty only if any of the other specified fields are present.
required_without:field_1,field_2,...
The field under validation must be present and not empty only when any of the other specified fields are not present.
required_with_all:field_1,field_2,...
The field under validation must be present and not empty only if all of the other specified fields are present.
required_without_all:field_1,field_2,...
The field under validation must be present and not empty only when all of the other specified fields are not present.
uploaded_file:min_size,max_size,extension_a,extension_b,...
This rule will validate data from $_FILES.
Field under this rule must be follows rules below to be valid:
$_FILES['key']['error'] must be UPLOAD_ERR_OK or UPLOAD_ERR_NO_FILE. For UPLOAD_ERR_NO_FILE you can validate it with required rule.Here are some example definitions and explanations:
uploaded_file: uploaded file is optional. When it is not empty, it must be ERR_UPLOAD_OK.required|uploaded_file: uploaded file is required, and it must be ERR_UPLOAD_OK.uploaded_file:0,1M: uploaded file size must be between 0 - 1 MB, but uploaded file is optional.required|uploaded_file:0,1M,png,jpeg: uploaded file size must be between 0 - 1MB and mime types must be image/jpeg or image/png.Optionally, if you want to have separate error message between size and type validation.
You can use mimes rule to validate file types, and min, max, or between to validate it's
No open issues yet, or sync has not completed.