Approach 2 superseeds Approach 1, and I like that it is explicit and adheres to the Principle of Least Surprise, unlike 3-4. Just looking at the injection rules gives you a hint it's going to surprise some people.
If injecting the constructor solves the heavy-dependency problem with approach 2 I don't really see a clear necessity to complicate things as in Approach 4, only to have to document "best practices" later (that will often 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 To unsubscribe from this group, send email to symfony-devs+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
