Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a cakephp2 app and the controllers are getting really big. Is there a best practice for breaking out bits of code into other functions that are not supposed to be actions?
*Sorry it has been a looong time since I did this with cakephp1.0 and back then I think I called them _functionname, which seems wrong these days.*
If you controller has been growing uncontrollably, then it has accumulated domain business logic and/or presentation logic.
The solution would be to move domain logic back into model layer. Either put that functionality in
AppModelclasses (which might be problematic, since it uses Active Record (anti)pattern), or create higher order structures, that do not extentAppModeland instead would act as services from proper model layer implementation.And presentation logic should go back into the views (or since you are using the Rails parody of MVC – in the view helpers).