This validator allow to check that the entity is consistent between user
associated with the entity, and the scope.
The entity is consistent if the user associated can reach the scope for the
ROLE "SEE/SHOW".
This is a Constraint with scope Class. Example of utilisation:
```
@UserCircleConsistency(
* "CHILL_TASK_TASK_SEE",
* getUserFunction="getAssignee",
* path="circle"
* )
class MyEntity {
// ...
public function getAssignee() {
// return user
}
}
```
Lists does not supports aggregators.
The export manager will filter the aggregators applying on the export
depending on the interface implemented by the export: if the export implements
`Export\ListInterface`, no aggregators will be returned for this export.
The search controller return a subset of the 5 first results. If the user want to
see more, the services implementing SearchInterface should add a link "see more",
and make use of the Pagination API to paginate.
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
