From 8b3a09120b2732894c18b45c785d36a3b141c69c Mon Sep 17 00:00:00 2001 From: Adrien Crivelli Date: Tue, 19 Sep 2023 10:40:35 +0200 Subject: [PATCH] Fix bullet list layout --- docs/en/reference/events.rst | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/en/reference/events.rst b/docs/en/reference/events.rst index 97f3d18962f..40dea522329 100644 --- a/docs/en/reference/events.rst +++ b/docs/en/reference/events.rst @@ -457,13 +457,12 @@ prePersist There are two ways for the ``prePersist`` event to be triggered: -- One is obviously when you call ``EntityManager::persist()``. The -event is also called for all :ref:`cascaded associations`. -- The other is inside the -``flush()`` method when changes to associations are computed and -this association is marked as :ref:`cascade: persist`. Any new entity found -during this operation is also persisted and ``prePersist`` called -on it. This is called :ref:`persistence by reachability`. +- One is when you call ``EntityManager::persist()``. The + event is also called for all :ref:`cascaded associations`. +- The other is inside the ``flush()`` method when changes to associations are computed and + this association is marked as :ref:`cascade: persist`. Any new entity found + during this operation is also persisted and ``prePersist`` called + on it. This is called :ref:`persistence by reachability`. In both cases you get passed a ``PrePersistEventArgs`` instance which has access to the entity and the entity manager.