Thanks, having validation in models not a deal breaker at this point .

Tarique


On Mon, Mar 10, 2014 at 3:05 PM, José Lorenzo <[email protected]> wrote:

> There is no convention right now, but you could make the method
> validationDefault in your table return an instance of any validator class,
> you could without too much hassle just instantiate the validator class
> matching the table name. In the controller you then would do:
>
> $validator = $this->Posts->validator();
> if ($entity->validate($validator)) {
> ... do something after validation ...
> }
>
> That is equivalent to doing:
>
> if ($this->Posts->validate($entity)) {
> ... do something after validation ...
> }
>
> Which seems more terse to me.
>
>
> On Monday, March 10, 2014 7:36:24 AM UTC+1, Dr. Tarique Sani wrote:
>
>> I was just thinking something like
>>
>> if ($this->validation->passes()) { do save or whatever }
>>
>> Anyway - nice to know that we will have automatic loading of Model and
>> Table classes. In fact I can confirm that if there is a PostsTable.php with
>> appropriate code it is available to the PostsController and we can do old
>> stuff like
>>
>> $posts = $this->Posts->find('all');
>> $this->set(compact('posts'));
>>
>> Cool and Thanks
>>
>> Tarique
>>
>>
>>
>> On Sat, Mar 8, 2014 at 8:25 PM, mark_story <[email protected]> wrote:
>>
>>> There are still conventions for loading model/table classes in the
>>> controller with the same name, but nothing for validators.
>>>
>>> Right now validators are built in the table classes and applied to
>>> entity data during saving. While it is not required to put validations into
>>> a class that is an option people can use. How would a controller using a
>>> validator work? Wouldn't that make it harder to apply validation when one
>>> model alters the data of another?
>>>
>>> -mark
>>>
>>> --
>>> Like Us on FaceBook https://www.facebook.com/CakePHP
>>> Find us on Twitter http://twitter.com/CakePHP
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "CakePHP" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>>
>>> Visit this group at http://groups.google.com/group/cake-php.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> =============================================================
>> The Conference Schedule Creator : http://shdlr.com
>>
>> PHP for E-Biz : http://sanisoft.com
>> =============================================================
>>
>  --
> Like Us on FaceBook https://www.facebook.com/CakePHP
> Find us on Twitter http://twitter.com/CakePHP
>
> ---
> You received this message because you are subscribed to the Google Groups
> "CakePHP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/cake-php.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
=============================================================
The Conference Schedule Creator : http://shdlr.com

PHP for E-Biz : http://sanisoft.com
=============================================================

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.

Reply via email to