Single file version available here.
Last updated on 2008-05-28.
To discuss, comment here.
| Prev | ||
| Home |
http://www.symfony-project.org/forum/index.php?t=msg&goto=23146&#msg_23146
"If the size of an action class grows too much, you probably need to do some refactoring and move some code to the model layer." http://www.symfony-project.org/book/trunk/06-Inside-the-Controller-Layer#The%20Action%20Class
The question is, how do I do that?
I mean, how to translate action's $this, e.g.,
$this->getUser()... $this->getRequestParameter...
I guess this question is so common-sense to PHP that it is not even covered in the book (controller & model section).
> $this->getUser()... > $this->getRequestParameter...
sfContext::getInstance()->getUser() sfContext::getInstance()->getRequest()->getParameter
This is "is just a little messy, and quite repetitive if used more than once.".
If you want to solve it systematically, ie, to "farm out action logic to static functions in a class in my application or module lib/ directory.", check out this:
http://www.symfony-project.org/snippets/snippet/113
documented on: 06 March 2007, sfxpt