This repository has been archived on 2023-08-20. You can view files and clone it, but cannot push or open issues or pull requests.
symfony/src/Symfony/Component/Form/FormEvents.php

95 lines
3.4 KiB
PHP
Raw Normal View History

<?php
/*
* This file is part of the Symfony package.
*
* (c) Fabien Potencier <fabien@symfony.com>
*
* For the full copyright and license information, please view the LICENSE
* file that was distributed with this source code.
*/
namespace Symfony\Component\Form;
/**
* 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}.
*
2012-05-26 08:48:33 +01:00
* @author Bernhard Schussek <bschussek@gmail.com>
*/
final class FormEvents
{
2014-10-23 13:21:59 +01:00
/**
2014-11-17 13:53:37 +00:00
* 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.
*
* @Event("Symfony\Component\Form\Event\PreSubmitEvent")
2014-10-23 13:21:59 +01:00
*/
const PRE_SUBMIT = 'form.pre_submit';
2014-10-23 13:21:59 +01:00
/**
2019-03-12 20:16:42 +00:00
* 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.
2014-11-17 13:53:37 +00:00
*
2019-03-12 20:16:42 +00:00
* 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.
2014-11-17 13:53:37 +00:00
*
* @Event("Symfony\Component\Form\Event\SubmitEvent")
2014-10-23 13:21:59 +01:00
*/
const SUBMIT = 'form.submit';
2014-10-23 13:21:59 +01:00
/**
2019-03-12 20:16:42 +00:00
* 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.
2014-11-17 13:53:37 +00:00
*
* It can be used to fetch data after denormalization.
*
2019-03-12 20:16:42 +00:00
* The event attaches the current view data. To know whether this is the renormalized data
* or the invalid request data, call Form::isSynchronized() first.
*
* @Event("Symfony\Component\Form\Event\PostSubmitEvent")
2014-10-23 13:21:59 +01:00
*/
const POST_SUBMIT = 'form.post_submit';
2014-10-23 13:21:59 +01:00
/**
2014-11-17 13:53:37 +00:00
* 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;
2019-03-12 20:16:42 +00:00
* - Keep synchronized the form depending on the data (adding or removing fields dynamically).
2014-11-17 13:53:37 +00:00
*
* @Event("Symfony\Component\Form\Event\PreSetDataEvent")
2014-10-23 13:21:59 +01:00
*/
const PRE_SET_DATA = 'form.pre_set_data';
2014-10-23 13:21:59 +01:00
/**
2014-11-17 13:53:37 +00:00
* The FormEvents::POST_SET_DATA event is dispatched at the end of the Form::setData() method.
*
2019-03-12 20:16:42 +00:00
* 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.
2014-11-17 13:53:37 +00:00
*
* @Event("Symfony\Component\Form\Event\PostSetDataEvent")
2014-10-23 13:21:59 +01:00
*/
const POST_SET_DATA = 'form.post_set_data';
private function __construct()
{
}
}