Symfony: 11 – Forms

The best practice is to build the form in a separate, standalone PHP class, which can then be reused anywhere in your application. This new class contains all the directions needed to create the task form. It can be used to quickly build a form object in the controller. // src/AppBundle/Form/Type/TaskType.php namespace AppBundle\Form\Type;   use
Continue reading Symfony: 11 – Forms

Symfony: 8 – Annotations

Annotations The default Symfony2 FrameworkBundle implements a basic but robust and flexible MVC framework. SensioFrameworkExtraBundle extends it to add sweet conventions and annotations. It allows for more concise controllers. Download the bundle and put it under the Sensio\Bundle\ namespace. Then, like for any other bundle, include it in your Kernel class. If you plan to
Continue reading Symfony: 8 – Annotations

Symfony: 4 – Configuration

Application configuration An application consists of a collection of bundles representing all of the features and capabilities of your application. Each bundle can be customized via configuration files written in YAML, XML or PHP. By default, the main configuration file lives in the app/config/ directory and is called either config.yml, config.xml or config.php depending on
Continue reading Symfony: 4 – Configuration

Symfony: 5 – Environments

Environments Every Symfony application runs within an environment. An environment is a specific set of configuration and loaded bundles, represented by a string. The same application can be run with different configurations by running the application in different environments. Symfony2 comes with three environments defined — dev, test and prod — but you can create
Continue reading Symfony: 5 – Environments