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


On Sat, Jan 22, 2011 at 3:23 PM, Jordi Boggiano <[email protected]> wrote:

> On 22.01.2011 21:50, Fabien Potencier wrote:
> > Parameters are more low-level and should not be used if there is a DIC
> > extension.
> >
> > Of course, when you define your own services and parameters, the story
> > is different. In that case, you don't need to create an extension
> > (except if you want to distribute your code). So, parameters become the
> > way you can tweak your services.
>
> I think he's onto something. If the "config.xml" files define parameters
> that are actually just used by the Extension class and then discarded, I
> think this leads to false expectations that you can define the parameter
> in your config file and override some value.
>
> It's just a best practice thing, but I think it makes sense that a
> parameter that is only accessible via the Extension config block should
> not be defined as a parameter in the DIC config. I have no idea how
> common this "bad practice" is at the moment though.
>
> Cheers
>
> --
> Jordi Boggiano
> @seldaek :: http://seld.be/
>
> --
> 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]<symfony-devs%[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

Reply via email to