On 23.09.2010 08:43, Fabien Potencier wrote: > I don't want to force the usage of services as controllers as it means > that you need to add a new service in the configuration each time you > create a new controller. That's just too much work for beginners and too > many things to understand to get started. That should be an option > though for all the reasons you and some others mentioned.
I'm not sure it's worth it for beginners tbh. I mean it's only good for a "build your symfony hello world in 10minutes" article, but beyond that people will be forced to go in the config to enable a service, or change a parameter, and sooner or later they'll most likely have to be able to create bundles and know about the whole service definition. I just think it might send the wrong signal to people and that later they have to do it right and convert all their routes, define all their controllers as services and change their controllers to use injected services instead of receiving the SC. I'd rather have a slightly steeper learning curve without gotchas later on. Thanks for the patch though, great to see that it's at least doable for those that want now to define their controllers as services. Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- 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
