Please NOT require always to return a response. I like to implement my own magic :-)
On Sun, 20 Feb 2011 22:21:46 +0100 Lukas Kahwe Smith <[email protected]> wrote: > Hi, > > I probably should have checked out the core.view [1] event earlier given the > ViewBundle [2] I have been working on for so long. However I do not really > like how it works atm. For one I dont like this approach of only triggering > it if the action doesnt return a Response instance. This sounds ugly and > magic to me, very symfony 1.x. I don't think it makes sense to allow > controllers that require a core.view event consumer that isnt part of the > controller itself, though I am not sure if this can be fixed. But maybe a > first step would be to always require returning a response [3] and simply > expecting to embed the parameters inside the Response. > > regards, > Lukas Kahwe Smith > [email protected] > > [1] > https://github.com/fabpot/symfony/blob/master/src/Symfony/Component/HttpKernel/HttpKernel.php#L110 > [2] https://github.com/liip/ViewBundle > [3] well actually I prefer the eager response model, but in that case actions > return values should imho just be ignored > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > 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 > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
