Skip to content

Commit

Permalink
Fixing coding standards violations in util\Validator.
Browse files Browse the repository at this point in the history
  • Loading branch information
jperras committed Jun 2, 2010
1 parent 6a0de5e commit 470d76e
Showing 1 changed file with 8 additions and 6 deletions.
14 changes: 8 additions & 6 deletions libraries/lithium/util/Validator.php
Expand Up @@ -321,6 +321,7 @@ public static function __callStatic($method, $args = array()) {
* array('notEmpty', 'message' => 'You must include credit card number'), * array('notEmpty', 'message' => 'You must include credit card number'),
* array('creditCard', 'message' => 'Your credit card number must be valid') * array('creditCard', 'message' => 'Your credit card number must be valid')
* ));` * ));`
* @param array $options Validator-specific options.
* *
* Each rule defined as an array can contain any of the following settings (in addition to the * Each rule defined as an array can contain any of the following settings (in addition to the
* first value, which represents the rule to be used): * first value, which represents the rule to be used):
Expand Down Expand Up @@ -415,12 +416,13 @@ public static function check(array $values, array $rules, array $options = array
* - `$value` _mixed_: This is the actual value to be validated (as in the above example). * - `$value` _mixed_: This is the actual value to be validated (as in the above example).
* - `$format` _string_: Often, validation rules come in multiple "formats", for example: * - `$format` _string_: Often, validation rules come in multiple "formats", for example:
* postal codes, which vary by country or region. Defining multiple formats allows you to * postal codes, which vary by country or region. Defining multiple formats allows you to
* retian flexibility in how you validate data. In cases where a user's country of origin is * retian flexibility in how you validate data. In cases where a user's country of origin
* known, the appropriate validation rule may be selected. In cases where it is not known, * is known, the appropriate validation rule may be selected. In cases where it is not
* the value of `$format` may be `'any'`, which should pass if any format matches. In cases * known, the value of `$format` may be `'any'`, which should pass if any format matches.
* where validation rule formats are not mutually exclusive, the value may be `'all'`, in * In cases where validation rule formats are not mutually exclusive, the value may be
* which case all must match. * `'all'`, in which case all must match.
* - `$options` _array_: This parameter allows a validation rule to implement custom options. * - `$options` _array_: This parameter allows a validation rule to implement custom
* options.
* *
* @see lithium\util\Validator::$_rules * @see lithium\util\Validator::$_rules
* @param mixed $name The name of the validation rule (string), or an array of key/value pairs * @param mixed $name The name of the validation rule (string), or an array of key/value pairs
Expand Down

0 comments on commit 470d76e

Please sign in to comment.