I'd like to see the following topic: Security Component Improvements Basically summed up here: http://groups.google.com/group/symfony-devs/msg/26113efc1207b30a
Johannes On 9 Nov., 19:01, Jordi Boggiano <[email protected]> wrote: > Here is my proposal for a topic: > > Recommended config file format: Yaml please :) > > State: > > At the moment XML is the recommended default afaik. > > Advantages of XML are: > > - Validation at the code level (is this really done?) > - IDE support for validation and auto-completion > > Disadvantages: > > - Pretty bloated syntax compared to Yaml > - IDE support seems to be a myth to me, I never saw anyone really use a > proper XML editor, so while this is theoretically possible, if nobody > does it it doesn't count imo. > > Advantages of Yaml: > > - Short and compact syntax, no namespace complexity > - Fast to learn (provided we deliver a good documentation that says > that ~ is null and things like that) > - Broader support amongst developers (iirc, sorry if my brain remembers > what he wants) > > Disadvantage: > > - No validation, but could be fixed by porting Kwalify [1] to php (I'm > willing to do it) > > I hope it's not too biased to begin with, but anyways this is what I > remember from reading/discussing the topic, and it'd be great to settle > on something already before we start to have too many bundles out there. > > [1]http://www.kuwata-lab.com/kwalify/ > > 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
