On Sep 29, 1:33 pm, Lukas Kahwe Smith <[email protected]> wrote: > On 29.09.2010, at 10:27, Francois Zaninotto wrote: > > then again it could just mean that someone could try to implement applying > XSD validation directly on yaml aka interpreting the XSD rules and then > checking the yaml if it passes. we might just support a subset of XSD for the > time being which might cover most use cases already .. not sure .. just > thinking allowed here.
A co-worker of mine just suggested this while I was sharing an XSD a made for a bundle I'm working on. I think that's definitely do-able, and would make for a great Symfony2 console command. It wouldn't necessarily have to map back to a specific line in the YML, rather the XSD could validate the entire configuration once it is loaded by various drivers (XML, YML, PHP, annotations) and then report errors such as "validation: enabled expected boolean, string given". A side-benefit of this would be only requiring bundle developers to make a single file to serve multiple purposes, vs. additional schema/ validation files in whatever format to validate YML, PHP, and other formats. Thought perhaps this is a mis-use of XSD? -- 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
