Download the PHP package wscore/validation without Composer

Validation

A validation component, designed for multi-byte (i.e. Japanese language) support. Features includes, such as:

• works well with code completion.
• multiple values combined to a single value (ex: bd_y, bd_m, bd_d to bd).
• preset order of rules to apply. essential to handle Japanese characters.
• easy to code logic.

License

MIT License

PSR

PSR-1, PSR-2, and PSR-4.

Installation

Basic Usage

factory object

Use ValidationFactory to start validating an array. For instance,

validation

a sample code for validating an array,

• set($key) sets validation rules for $key.
• get($key) returns a validated value, or false if validation fails.
• getRules($key) returns an existing rules object to modify.
• fails() or passes() method will evaluate all rules and returns boolean if all validation rules has passed or not.
• getAll() returns all the value including the invalidated ones, whereas getSafe() returns only the validated values.
• getMessages() returns all the invalidated error messages.

types

The rule types are standard rules for the given validation type. Select validation type by as{Type}() after set method,

There are following predefined types that are compatible with HTML5 input types.

• binary
• text
• mail
• number
• integer
• float
• date
• datetime
• month
• tel

And there are some multiple filed types.

• dateYMD
• dateYM
• dateHis
• timeHis
• timeHi

which are defined in Locale/{locale}/validation.types.php file.

validation rules

There are many rules for validations. You can chain them as shown in previous example codes;

Available filters, i.e. that may alter the value:

• message(string $message): set error message.
• multiple(array $parameter): set multiple field inputs, such as Y, m, and d.
• array(): allows array input.
• noNull(bool $not = true): removes null character.
• encoding(string $encoding): validates on character encoding (default is UTF-8).
• mbConvert(string $type): converts kana-set (in Japanese).
  • mbToHankaku(): converts alpha-numeric zenkaku characters to hankaku.
  • mbToZenkaku(): converts alpha-numeric hankaku characters to zenkaku.
  • mbToHankakuKatakana(): converts zenkaku katakana to hankaku.
  • mbToHiragana(): converts katakana to zenkaku hiragana.
  • mbToKatakana(): converts hiragana to zenkaku katakana.
• trim(bool $trim = true): trims input string.
• sanitize(string $type): sanitize value.
  • sanitizeMail(): sanitize for mail input.
  • sanitizeFloat(): sanitize for floating number.
  • sanitizeInt(): sanitize for integer number.
  • sanitizeUrl(): sanitize for ULR input.
  • sanitizeString(): sanitize as a string.
• string(string $type): converts string to upper/lower/etc.
  • strToLower(): converts string to lower letters.
  • strToUpper(): converts string to upper letters.
  • strToCapital(): capitalizes a string.
• default(string $value): sets default value if not set.

All the verifiers, i.e. check if the value satisfies the requirements:

• required(bool $required = true): required value
• requiredIf(string $key, array $in=[]): set required if $key exists (or in $in).
• loopBreak(bool $break = true): breaks filter loop.
• code(string $type):
• maxLength(int $length): maximum character length.
• pattern(string $reg_expression): preg_match pattern
• matches(string $match_type): preset regex patterns (number, int, float, code, mail). using matches rules provides more specific error messages compared to patterns rule.
  • matchNumber(): matches for numeric input.
  • matchInteger(): matches for integer input.
  • matchFloat(): matches for floating number input.
  • matchCode(): matches for "[-_0-9a-zA-Z]".
  • matchMail(): matches for simple mail pattern.
• kanaType(string $match_type): checks kana-type.
  • mbOnlyKatakana(): verifies only zenkaku katakana.
  • mbOnlyHiragana(): verifies only zenkaku hiragana.
  • mbOnlyHankaku(): verifies only hankaku characters (i.e. ASCII).
  • mbOnlyHankakuKatakana(): verifies only hankaku katakana.
• min(int $min): minimum numeric value.
• max(int $max): maximum numeric value.
• range(array $range): range of [min, max].
• datetime(string|bool $format = true): checks for datetime with format.
• in(array $choices): checks for list of possible values.
• inKey(array $choices): checks if the value is defined in as keys (faster than in).
• confirm(string $key): confirm against another $key.

Advanced Features

validating a list of input

To validate a list of input data, such as checkbox, use array() rules as follows. When the validation fails, it returns the error message as array.

multiple inputs

WScore/Validation can handle separate input fields, such as date, as one input. For instance, date, dateYM, datetime types

use rules to construct own multiple inputs as,

where suffix lists the postfix for the inputs, and format is the format string using sprintf.

confirm to compare values

for password or email validation with two input fields to compare each other.

Please note that the actual input strings are different. They become identical after lowering the strings.

order of filter

some filter must be applied in certain order...

custom validation

Use a closure as custom validation filter.

You cannot pass parameter (the closure is the parameter). argument is the ValueTO object which can be used to handle error and messages.

Setting an error to ValueTO will break the filter loop, i.e. no further rules will be evaluated.

setting values and errors

To set a value, or an error to the validator, use setValue and setError methods.

Setting error will make fails() method to return true.

Modifying Error Messages

To use your own messages, create a directory such as your/path/<locale>, then, create or copy the following files.

• validation.filters.php
• validation.messages.php
• validation.types.php

The validation.messages.php file contains the default error messages as an array that looks like:

whereas the error messages are determined as follows:

1. message set by message rule,
2. method and parameter specific message,
3. method specific message,
4. type specific message, then,
5. general message

1. use message rule

use message method to set its message.

2. method and parameter specific message

some filters, matches and kanaType, has its message based on the parameter.

3. method specific message

some of the filters, such as required, has filter specific message.

4. type specific message

most of the rule types has its own messages.

5. general message

uses generic message, if all of the above rules fails.