+1 for yaml. XML is a hazard to write and when 99% of us dont have xml autocompletion it just dosent make sense. If xml is gonna be the default i at least thing that the two methods for xsd and namespace on dependency injection extensions should be removed be moved to a interface that is optional to implement (and make the equivilent methods for yaml for a kwalify port (if it gets ported)).
On 18 Nov., 00:39, Jordi Boggiano <[email protected]> wrote: > Heya, > > So.. as a followup to last's week IRC talk, where someone told me to > convert the security services definition from xml to yaml to see how > ugly it would get, I'd like to present you my findings: It's actually ok! ;) > > First of all, the base XML one:http://pastie.org/1307034 > Second, the Yamlified version:http://pastie.org/1307035 > > Seeing that, what do you guys think? Do you really think XML is worth it? > > ======= > > Another somewhat related issue btw that someone came to talk about on > IRC, if you got the following DBAL config, you can't just override the > dbname in your config_test.xml, you have to redefine the entire tag, > duplicating all attributes: > > <doctrine:dbal dbname="" user="" password="" host="" /> > > With Yaml it is very easy to just override one entry with: > > doctrine.dbal: > dbname: testingdb > > If anyone has a clue how to address that in XML please speak up. > > 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
