Heya, I am wondering if it really makes sense to have:
twig.config: orm.config: ext.config: .. I see the point that one extension could have more than configLoad(), it could have fooLoad() and then use: ext.foo: But.. is it really useful? It seems that everyone more or less standardized on using *.config, so imo we could remove it and let it just be: twig: orm: ext: What do you think? Of course the only problem is if someone names their extension parameters or services, then it conflicts, but we could easily mark those as reserved. There is also the case of XML, where twig.config is twig:config, which is a namespace; I guess in that case it makes a bit more sense, but I'm not sure what it'd mean to remove the namespace. Losing XSD capability? 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
