The ``path`` option is new in Symfony 2.2, ``pattern`` is used in older

The ``methods`` option is added in Symfony 2.2. Use the ``_method``

that should live in the ``Tests/`` subdirectory of your bundles. If you follow

``app/phpunit.xml.dist`` file. You can edit this file to change the defaults or

create an ``app/phpunit.xml`` file to setup a configuration for your local

machine only.

Store the ``phpunit.xml.dist`` file in your code repository and ignore the

By default, only the tests from your own custom bundles stored in the standard

directories ``src/*/*Bundle/Tests`` or ``src/*/Bundle/*Bundle/Tests`` are run

by the ``phpunit`` command, as configured in the ``phpunit.xml.dist`` file:

But you can easily add more directories. For instance, the following

configuration adds tests from a custom ``lib/tests`` directory:

.. code-block:: xml

* The type name (one of the :doc:`form types </reference/forms/types>`);

This way you can build a tree of routes. Additionally you can define a prefix

and default values for the parameters, requirements, options, schemes and the

host to all routes of a subtree using methods provided by the

``RouteCollection`` class::

:method:`Symfony\\Component\\Security\\Core\\Encoder\\BasePasswordEncoder::isPasswordTooLong`

method for this check::

:doc:`using Gmail </cookbook/email/gmail>` or similar services is not an

You can see that you need to listen on these two events and have different

callbacks only because in two different scenarios, the data that you can use is

available in different events. Other than that, the listeners always perform

exactly the same things on a given form.

One piece that is still missing is the client-side updating of your form after

the sport is selected. This should be handled by making an AJAX call back to

your application. Assume that you have a sport meetup creation controller::

The associated template uses some JavaScript to update the ``position`` form

field according to the current selection in the ``sport`` field:

.. configuration-block::

.. code-block:: html+jinja

{# src/Acme/DemoBundle/Resources/views/Meetup/create.html.twig #}

{{ form_start(form) }}

{{ form_row(form.sport) }} {# <select id="meetup_sport" ... #}

{{ form_row(form.position) }} {# <select id="meetup_position" ... #}

{# ... #}

{{ form_end(form) }}

.. include:: /cookbook/form/dynamic_form_modification_ajax_js.rst.inc

.. code-block:: html+php

<!-- src/Acme/DemoBundle/Resources/views/Meetup/create.html.php -->

<?php echo $view['form']->start($form) ?>

<?php echo $view['form']->row($form['sport']) ?> <!-- <select id="meetup_sport" ... -->

<?php echo $view['form']->row($form['position']) ?> <!-- <select id="meetup_position" ... -->

<!-- ... -->

<?php echo $view['form']->end($form) ?>

.. include:: /cookbook/form/dynamic_form_modification_ajax_js.rst.inc

The major benefit of submitting the whole form to just extract the updated

``position`` field is that no additional server-side code is needed; all the

code from above to generate the submitted form can be reused.

<script>

var $sport = $('#meetup_sport');

$sport.change(function(){

// ... retrieve the corresponding form.

var $form = $(this).closest('form');

// Simulate form data, but only include the selected sport value.

var data = {};

data[$sport.attr('name')] = $sport.val();

// Submit data via AJAX to the form's action path.

$.ajax({

url : $form.attr('action'),

type: $form.attr('method'),

data : data,

success: function(html) {

// Replace current position field ...

$('#meetup_position').replaceWith(

// ... with the returned one from the AJAX response.

$(html).find('#meetup_position')

);

// Position field now displays the appropriate positions.

}

});

});

</script>