The Form object is passed as an argument to that method (see next example).

You can also define whole logic inline by using a ``Closure``::

group which is being used. If you want to validate the default constraints

of the entity as well you have to adjust the option as follows::

Additionally, if there are any fields on the form that aren't included in

{# app/Resources/views/default/new.html.twig #}

{% form_theme form 'form/fields.html.twig' %}

{% form_theme form 'form/fields.html.twig' 'form/fields2.html.twig' %}

{# ... render the form #}

<!-- app/Resources/views/default/new.html.php -->

<?php $view['form']->setTheme($form, array('form')) ?>

<?php $view['form']->setTheme($form, array('form', 'form2')) ?>

<!-- ... render the form -->

web designers everywhere.

Twig can also do things that PHP can't, such as whitespace control,

and the inclusion of custom functions and filters that only affect templates.

Twig contains little features that make writing templates easier and more concise.

Take the following example, which combines a loop with a logical ``if``

<div id="sidebar">

{% block sidebar %}

<ul>

</ul>

{% endblock %}

</div>

{# ... #}

<div id="sidebar">

{{ render(controller(

{ 'max': 3 }

)) }}

</div>

<div id="sidebar">

<?php echo $view['actions']->render(

new \Symfony\Component\HttpKernel\Controller\ControllerReference(

array('max' => 3)

)

) ?>

<img src="{{ asset('images/logo.png') }}" alt="Symfony!" />

.. code-block:: html+php

<img src="<?php echo $view['assets']->getUrl('images/logo.png') ?>" alt="Symfony!" />

The ``asset`` function's main purpose is to make your application more portable.

If your application lives at the root of your host (e.g. http://example.com),

.. code-block:: html+jinja

The end result is a page that includes both the ``main.css`` and ``contact.css``

stylesheets.

method works perfectly with the three different types of templates that were just

covered:

layout for your application (like in the previous example). Internally, this

template is called ``base.html.twig``;

.. code-block:: html

The Twig and PHP templating systems approach the problem in different ways.

If you're using Twig, output escaping is on by default and you're protected.

Do you also want to participate in the Symfony Documentation? Take a look

at the ":doc:`/contributing/documentation/overview`" article.

April, 2015

.. code-block:: bash

Afterwards compile your container and check to make sure that you get

a proxy for your lazy services.