class
FormEvents
To learn more about how form events work check the documentation
entry at {@link https://symfony.com/doc/any/components/form/form_events.html}.
To learn how to dynamically modify forms using events check the cookbook
entry at {@link https://symfony.com/doc/any/cookbook/form/dynamic_form_modification.html}.
Constants
PRE_SUBMIT |
The PRE_SUBMIT event is dispatched at the beginning of the Form::submit() method.
It can be used to:
- Change data from the request, before submitting the data to the form.
- Add or remove form fields, before submitting the data to the form.
|
SUBMIT |
The SUBMIT event is dispatched after the Form::submit() method
has changed the view data by the request data, or submitted and mapped
the children if the form is compound, and after reverse transformation
to normalized representation.
It's also dispatched just before the Form::submit() method transforms back
the normalized data to the model and view data.
So at this stage children of compound forms are submitted and synchronized, unless
their transformation failed, but a parent would still be at the PRE_SUBMIT level.
Since the current form is not synchronized yet, it is still possible to add and
remove fields.
|
POST_SUBMIT |
The FormEvents::POST_SUBMIT event is dispatched at the very end of the Form::submit().
It this stage the model and view data may have been denormalized. Otherwise the form
is desynchronized because transformation failed during submission.
It can be used to fetch data after denormalization.
The event attaches the current view data. To know whether this is the renormalized data
or the invalid request data, call Form::isSynchronized() first.
|
PRE_SET_DATA |
The FormEvents::PRE_SET_DATA event is dispatched at the beginning of the Form::setData() method.
It can be used to:
- Modify the data given during pre-population;
- Keep synchronized the form depending on the data (adding or removing fields dynamically).
|
POST_SET_DATA |
The FormEvents::POST_SET_DATA event is dispatched at the end of the Form::setData() method.
This event can be used to modify the form depending on the final state of the underlying data
accessible in every representation: model, normalized and view.
|
ALIASES |
Event aliases.
These aliases can be consumed by RegisterListenersPass.
|