Hi, I'm currently working on my own action base class extending sfActions to integrate some features I often need in my actions.
One thing is related to execution of action methods and I wonder if you are interested in a) having this as plugin or b) integrating it into symfony? What I did is following: - You can define initActionName() methods. --> Executed before validation and execution of the respective action (within initialize). - You can define prepareActionName() methods. --> Executed by preExecute() before execution of the respective action. - You can define executeActionNameRequestmethod(), (e.g. executeEditGet() or executeEditPost()) --> Executed by execute() if such a method exists otherwise the good old executeEdit() is executed. What do you think about this additional "execution magic" ? It saves me from writing tons of request method checks and makes my code more readable and gives me more flexibilities with complex actions. I wonder if the naming scheme of the request method magic is good or if another scheme would be better - like getExecuteActionName() / postExecuteActionName() - but I think this would be confusing in context of preExecute / postExecute. Regards, Matthias --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
