2011/1/20 Dan Leech <[email protected]>: > On a similar note, yesterday, to facilitate displaying certain fields > depending on the users security roles, I injected the security.context > into the constructor of the form in the DIC (best practice??). But > overloading the constructor was a little cumbersome, and I would > rather have set the `security.context` via. a method call.
Can you show me some code? > It crossed my mind that life might be made a little easier by having > an "init()" method to call after having called any post-constructor > setters. But I can see the argument for not having this. I thought about that already, but didn't find enough use cases to justify this refactoring (yet). 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
