On 4/21/11 10:31 AM, Lukas Kahwe Smith wrote:
On 21.04.2011, at 10:24, Bernhard Schussek wrote:
Without taking a deeper look at the matter here, I'm very much against
introduction of *Light bundles. If usage can be simplified, it should
be simplified in the core. Otherwise we end up with too many ways to
do the same thing.
We can support the "simple mode" in SecurityBundle too.
Basically we would need to then first introspect the configuration if "simple
mode" is enabled (or not disabled) by iterating over the configuration once and then
switch to a different Configuration class depending on this. If we keep this all in one
Configuration class we would have to relax/complicate the validation which isnt
acceptable.
Having a Light Bundle would get around this as the "flag" to enable simply mode
would be the alias name in the app config.
Anyway, as I begin to notice a pattern, where I seem to repeatedly attempt to
explain that this isnt about duplication etc and everybody disagreeing I will
stop here. If you all feel like documentation can solve the issue, then I
concede.
I think updating the documentation is the first required step before
anything else (and when writing documentation, we almost always change
the code to make it better/simpler/...). If documentation does not solve
all problems, then we will need to see how we can change the current
bundle to ease things.
Fabien
regards,
Lukas Kahwe Smith
[email protected]
--
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
