Sarke

Sorry about that, I will do in the future. Yeah, I've used some code analyzers and they don't like the size of my models either. I think Yii is more in the "fat models, thin controllers" camp, but it also has Behaviors and Events that attach to them. I will refactor it to use services (or something else), thank you for your advice. I do realize I can use the inline phpdoc blocks every time I use it, but I would much rather set this up once for each model so the IDE knows what the class really is. The issue is how Yii2 handles relations. In Yii1 the relations wo

If you have a suggestion, let's hear it. If I extend the models I don't need to use the traits to store model-specific code. The latter is more of a workaround. That doesn't mean I am not using traits in other places. I am using Smarty views for all my HTML output. Or are you talking about view classes for each model, in which case would you elaborate? I don't see how model getters and such would be appropriate in a view.

This is a post I made on the Yii forum, but it pertains to PHP in general as well. Any advice or insight would be appreciated. --- So, I have different aspects of the app: front-end ui module, output generation (pdf reports, etc), console commands and workers. Using the standard examples, let's say we have Book and Author models. These would all reside in /app/models/. Now, the issue is that there is tons of code that need to go into these models that relate only to the ui. There's tons that relate only to the output generation, etc. So to organise this I see a few options: 1. Pu

Thanks for your input. I will continue to use my style of choice. Weirdo...

I like my braces style and I like my tabs. But I also realize there is benefit to using PSR-2 for more standard code when it comes to collaborating and contributing to open-source (some of which demand it). What compelling arguments can you make that I should switch to PSR-2 for all my PHP coding?