Php classes ... check

Question

im does a php check class with additional classes that extend it, e.g. mobile, suburbs, credit_card, ect

So the idea is that you can call

$validation = new Validation('mobile'); $valid = $validation->validate($number); $validation->type('suburb'); $valid2 = $validation->validate($suburb); 

now my idea for this is to

 class Validation() { private $v_type = null; function __construct($type) { $this->type($type); } public function type($type) { $this->v_type = new $type(); } public function validate($info) { return $this->v_type->validate($info); } } 

as a very simple example

but is there a better way to do this?

Answer 1

You could do it that way, but it could be improved. Having the actual capsule of validators, their own validation logic is good. Extending them from the base class is not. Let it implement an interface instead. Thus, any class can be a Validator.

 interface IValidate { public function validate($value); } 

Your validators will look like this:

 class IsNumeric implements IValidate { public function validate($value) { return is_numeric($value); } } 

and

 class GreaterThan implements IValidate { protected $_value; public function __construct($value) { $this->_value = $value; } public function validate($value) { return $value > $this->_value; } } 

You will still have the main Validator class. Unlike your example, the Validator below accepts several Validators, which allows you to create a filter chain.

 class Validator implements IValidate { protected $_validators; public function addValidator(IValidate $validator) { $this->_validators[] = $validator; return $this; } public function validate($value) { foreach($this->_validators as $validator) { if ($validator->validate($value) === FALSE) { return FALSE; } } return TRUE; } } 

And it can be used as:

 $validator = new Validator; $validator->addValidator(new IsNumeric) ->addValidator(new GreaterThan(5)); var_dump( $validator->validate('ten') ); // FALSE var_dump( $validator->validate('10') ); // TRUE var_dump( $validator->validate('1') ); // FALSE 

The above is mainly a Team Template . And due to the fact that Validator implements Ivalidate, it is also a Composite . You can take the Validator chain on top and put it in another Validator chain, for example

 $numericGreaterThanFive = new Validator; $numericGreaterThanFive->addValidator(new IsNumeric) ->addValidator(new GreaterThan(5)); $otherValidator = new Validator; $otherValidator->addValidator(new Foo) ->addValidator(new Bar) ->addValidator($numericGreatherThanFive); 

For convenience, you can add a static factory method to create validators with valid control command objects (as shown elsewhere).

On the side: Zend Framework already has a large number of validators that you can build on . Since ZF is a component library, you can use them without transferring the entire application to ZF.

Answer 2

Usually you do such things with the Factory pattern, something like this:

 class ValidatorFactory { public static function get($type) { $validator = "Validator_$type"; return new $validator(); } } $valid = ValidatorFactory::get('mobile')->validate($number); 

Of course, some error checking and the like will be required, but you should get an idea

Answer 3

 ... public function type($type) { return new self($type); } ... 

Note. Each time, each one returns a new instance of the Validator class, so it would be better to use the Factory template, as Dennis suggested or not bind the new Validator to type ().