For action which require a confirmation message.
This is a way to have a template for every confirmation message in the
app.
Example of usage :
```
{{ include('ChillMainBundle:Util:confirmation_template.html.twig',
{
# a title, not mandatory
'title' : 'Remove membership'|trans,
# a confirmation question, not mandatory
'confirm_question' : 'Are you sure you want to remove
membership of "%name%" from the group "%group%"?'|trans({ '%name%' :
person.firstname ~ ' ' ~ person.lastname, '%group%' :
membership.cgroup.name }),
# a route for "cancel" button (mandatory)
'cancel_route' : 'chill_group_membership_by_person',
# the parameters for 'cancel' route (default to {} )
'cancel_parameters' : { 'person_id' : membership.person.id
},
# the form which will send the deletion. This form
# **must** contains a SubmitType
'form' : form
} ) }}
```
Now, the function take into account that parent might be multiple.
This is still incomplete : I do not know if this work if the parent is
multiple **and** a select2
- add a test for 'generate' ;
- the ExportType declare keys, and those keys are used in ExportManager;
- the export interface does not require the "has form" function, and
export form is taken into account
The controller handle form validation. Each step is now responsible for validating his own form and, if valid, redirect to next step. The last step gather data from previous step and generate a redirection to an HTTP GET query to generate the report.
The controller does not have to handle data of the form ExportType. The ExportManager now handles those data. This is supposed to limit the number of place where the form data are handled.
