Thank's Florian, it seems to make sense. As I am still not using cake3, I thought of using "libs" because the App class allows loading of these.
Em sábado, 26 de setembro de 2015 10:25:05 UTC-3, Florian Krämer escreveu:
Read the first two answers here:I wouldn't call it lib, if you go for Cake3 just create a new namespace "App\Domain" and put your classes into that folder, maybe following a convention like other things as well. For example "ReservationsDomain.php".Check the ModelAwareTrait you could create a DomainAware trait that instantiates the Domains in your controllers as needed and automatically passes the request object to your domain objects.
On Friday, September 25, 2015 at 2:36:18 PM UTC+2, gersonfs wrote:Hello,Where the domain layer would fit better in a CakePHP APP? Models I believe it would not. It would be a generic PHP Class into a "Lib"?Thanks!
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 cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment