Events
======

An event mechanism is available to add an extra entry point to extend an Admin instance.

ConfigureEvent
~~~~~~~~~~~~~~

This event is generated when a form, list, show, datagrid is configured. The event names are:

 - ``sonata.admin.event.configure.form``
 - ``sonata.admin.event.configure.list``
 - ``sonata.admin.event.configure.datagrid``
 - ``sonata.admin.event.configure.show``

PersistenceEvent
~~~~~~~~~~~~~~~~

This event is generated when a persistency layer update, save or delete an object. The event names are:

 - ``sonata.admin.event.persistence.pre_update``
 - ``sonata.admin.event.persistence.post_update``
 - ``sonata.admin.event.persistence.pre_persist``
 - ``sonata.admin.event.persistence.post_persist``
 - ``sonata.admin.eventDeleting objects
================

.. note::

    This document is a stub representing a new work in progress. If you're reading 
    this you can help contribute, **no matter what your experience level with Sonata 
    is**. Check out the `issues on GitHub`_ for more information about how to get involved.

This document will cover the Delete action and any related configuration options.


Basic configuration
-------------------

To do:

- global (yml) options that affect the delete action
- a note about Routes and how disabling them disables the related action
- any Admin configuration options that affect delete
- a note about lifecycle events triggered by delete?

.. _`issues on Github`: https://github.com/sonata-project/SonataAdminBundle/issues/1519