A week of symfony #407 (13->19 October 2014)

This week, the new Symfony Best Practices were published, sparking an intense debate among the community. In addition, the new Symfony installer became a reality and hopefully it will be ready for the launch of Symfony 2.6.

Symfony2 development highlights

2.3 changelog:

  • c9cd76c: [Twig Bridge] added missing argument in the yaml_encode filter
  • 2ad0642: [FrameworkBundle] fixed IDE links for emacas and Sublime
  • 0af6467: [Form] enforce options value type check in some form types

2.5 changelog:

  • 2822fdb: [SecurityBundle] added trust_resolver variable into expression

Master changelog:

  • 3c401af: [VarDumper] enhanced dumping refs

Newest issues and pull requests

Twig development highlights

Master changelog:

  • 98f1a4b: Simplified Twig installation instructions
  • 0082e05: fixed the support of 2-word tests without a custom node class
  • bf541bf: fixed lexing of negative numbers

They talked about us

Comments

May I ask what this new installer has to offer, compared to running a simple "composer create-project symfony/framework-standard-edition" ?
@Marcel Hernandez: it will also perform additional Symfony2-specific checks. See https://github.com/symfony/symfony-installer/issues/9.
Marcel, here are the main advantages of the new installer:

* It doesn't require to have Composer installed.
* It's much simpler to use: "symfony new blog/" instead of "composer create-project symfony/framework-standard-ediion blog/"
* It's orders of magnitude faster than Composer. It takes around 10 seconds to install on a typical Internet connection.
* It doesn't ask anything to the user or bothers him/her with useless information.
* After installation, it checks if your system is ready to execute Symfony applications. If not, it will show you the exact error messages.
the new installer looks really promising.
Thank you all :)

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.