+1 for XML bundle configs - especially in redistributed code. Until a couple of weeks ago I LOATHED XML and always used YAML in my Symfony2 experiments. As my applications grow, I've come to rely on XML schema errors to alert me when I fat finger a config, which has bitten me in the ass with YAML and wasted hours of my life. "Best practices" really is best in this case.
Greg On Sep 7, 7:32 am, Fabien Potencier <fabien.potenc...@symfony- project.com> wrote: > On 9/7/10 2:05 PM, Jordi Boggiano wrote: > > > On 07.09.2010 13:57, Fabien Potencier wrote: > >> I have the answer for redistributable bundles: they must use XML as > >> their only way to provide configuration (as explained in the > >> documentation). Annotations must only be used for end-user code. > > > Which means you can't easily take your yml-configured code and publish > > it painlessly, you have to convert your entire config.. Not ideal. > > You can, but then, you aren't using the "best practices". And Symfony2 > gives you the tool to convert any format to any other one. > > Fabien -- 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
