Le 22/01/2011 23:14, ryan weaver a écrit :
Yes, Jordi, you understand me perfectly. I'm seeing this in the
MongoDB bundle, but perhaps the "bad practice" isn't very rampant.
I'll put together a pull request removing some of these parameters and
state my case there.
Fabien, I suppose the documentation should *just* document the
available "options" of a DIC and leave the discovery that lower-level
things could be overridden (such as service class names) to the
advanced developer. That gives me good "philosophical" direction as well.
Thanks!
Ryan Weaver
Lead Programmer - iostudio - Nashville, TN
http://www.iostudio.com
http://www.thatsquality.com
Twitter: @weaverryan
I think the best practice should be to allow to define through the DI
Extension all parameters that could be overrided.
Using an imported file to define the service is more readable in a
bundle than defining all the services in the extension.
--
Christophe | Stof
--
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
