Hi all,
This morning, I was working on making some Security things more
configurable, and so I have removed some SC (Service Container)
parameters to replace them with default values in the related
Configuration class. For instance:
https://github.com/symfony/symfony/commit/b638cf07a5865ed93efda9cf223d79897ee78277
On the one hand, it makes things "cleaner" and more consistent as
everything is now managed/configured via the Configuration class (you
cannot change things directly via a parameter anymore).
But on the other hand, it also makes some service definitions tied to
the SC extension (as you can see, security.authentication.listener.basic
for instance has 2 blank arguments that must be replaced by the extension).
So, before the change, it was possible to "just" include the XML file
and get working services (configured via the change of some parameter
values if needed). After the change, the XML file only makes sense when
used with the extension and the configuration classes.
As I will make some more similar changes elsewhere in the framework, I
just want to be sure that everybody is on the same page here. On a side
note, as we have also decided to remove most class parameters, it means
that the core framework will barely use parameters.
Any thoughts?
Fabien
--
Fabien Potencier
Sensio CEO - Symfony lead developer
sensiolabs.com | symfony.com | fabien.potencier.org
Tél: +33 1 40 99 80 80
--
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
