Check out the discussion here: https://github.com/FriendsOfSymfony/UserBundle/issues/154
t On Fri, May 20, 2011 at 00:58, dbenjamin <[email protected]> wrote: > Hi, > I'm testing the FOSUserBundle, and a question came to my mind. > If i want to remove the UserController dependency to the container, i will > need to inject every dependency, through the constructor for instance. > But, at some point, that can represents a lot of dependencies. > For instance, you have the UserFormHandler, ChangePasswordFormHandler, > ResetPasswordFormHandler ... > Plus, the controller needs also the Request, Templating, Router, > SecurityContext, UserManager, Mailer, some options. > It is a looot of dependencies to inject. > Even if removing the dependency to the container seems a good practice, i > don't know why, but i'm not so sure when i'm writing the constructor that it > is a way to go. And i don't talk about the overhead. > > And this leads me to a more generally subject: How do you generally deal > with that ? What's the Best Practice for you here ? > > > -- > Benjamin Dulau - anonymation CEO > anonymation.com | code.anonymation.com > [email protected] > > -- > 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
