Hi all, Jordi pushed me to raise my concerns here. I don't really have a solution yet, and maybe I'm the only one who sees these problems, but here we go:
I currently see a big problem with the design of the extensions in the DI container. As one can see for example in FrameworkExtension and SecurityExtension, these classes are by design huge and untestable. Especially their untestability is a big issue for me, because a little error can shut down your whole application and you won't notice. Furthermore, AFAIK services set in extension classes can't be overridden in other parts of the application. Is this correct? If yes, I can't imagine how this will not lead to problems. As I said, I don't really have a solution. Maybe more abstraction could help to reduce the amount of code written in the extension classes and make them more testable. Now is our last chance to get this right, otherwise we're stuck with this design for the next years. Please tell me what you think. Bernhard -- Software Architect & Engineer Blog: http://webmozarts.com Twitter: http://twitter.com/webmozart -- 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
