On Sat, Jan 29, 2011 at 2:19 PM, Fabien Potencier <[email protected]> wrote: > This is indeed a nice idea but that won't work for XML based configuration > as you can only have one XSD for a give XML namespace (correct me if I'm > wrong here).
I don't want to sound like a broken record but that is another good reason to get rid of XML config files.. I've been thinking, having bundle configurations as XML and application config as YML is really weird. People get used to the YML one and then you tell them just look in that bundle's config to find the services and they have to figure out another configuration type for no good reason. Besides the XSD is only used for application config validation, so if the best practice there is YML, the XSD stuff is really pointless imo. 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] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
