I wouldn't mind getting rid of the service:action notation :) I think its a hack. It makes the routing layer aware of differences of what a controller actually is. That however belongs to the controller resolver layer.
On Thu, 23 Jun 2011 04:42:51 -0700 (PDT) Michel Salib <michelsa...@gmail.com> wrote: > Beberlei, I see your point. But isn't it confusing to promote three way of > using controllers (a bad and easy one, a good and "hard" one and one in the > middle) ? > > It surly offers a good transition step to migrate controllers, but as you > said it is just a helper for a migration. I don't think it is a good thing > to include this kind of code into the framework. > > Again your idea is interesting, we could push some documentation about the > process of moving from a base-class controller to a proper service including > your suggested step. > > -- > 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 symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
