Ok I'm too sick to parse that code atm, but if you say it's good, then I guess it's ok.
The fever makes me stabby towards xml, nevermind. On 31.01.2011 11:24, Johannes wrote: > I don't think we have to drop anything ;) > > If we add something like https://github.com/fabpot/symfony/pull/554, > it will be very easy to support different formats without having to > worry much about their distinctions. Plus, we would have a > standardized way of how configs are handled instead of each extension > implementing some custom logic. > > Kind regards, > Johannes > > On Jan 31, 11:18 am, Jordi Boggiano <[email protected]> wrote: >> Nobody seems to want to answer my concerns with the mess of having xml >> and yaml configurations, but whatever, I got a new idea reading Ryan's mail. >> >> Couldn't we drop XML for app config? That would simplify the extension >> normalization requirements quite a lot, if they had to only support yaml. >> >> Service definitions in bundles can still be done in XML for all I care, >> this is normalized at the framework level so no problem. It's still a >> bit of a shame that users that want to override a service have to parse >> the xml into yaml (at least those that don't want to use xml..) but this >> isn't too common use case I guess, so it's not too bad. >> >> Thoughts? >> >> Cheers >> >> -- >> Jordi Boggiano >> @seldaek ::http://seld.be/ > -- 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
