- Issue created by @phenaproxima
- Status changed to Needs review
5 months ago 2:52pm 16 April 2024 - Status changed to RTBC
5 months ago 3:38pm 16 April 2024 - π¬π§United Kingdom alexpott πͺπΊπ
Can we add a note to the recipes.api.php issue to document this?
- Status changed to Fixed
5 months ago 3:42pm 16 April 2024 - π¬π§United Kingdom alexpott πͺπΊπ
Committed and pushed 19dd1f33379 to 11.x and 72926a564fd to 10.3.x. Thanks!
diff --git a/core/lib/Drupal/Core/Recipe/RecipeAppliedEvent.php b/core/lib/Drupal/Core/Recipe/RecipeAppliedEvent.php index cf2a94fb3b7..251139058cb 100644 --- a/core/lib/Drupal/Core/Recipe/RecipeAppliedEvent.php +++ b/core/lib/Drupal/Core/Recipe/RecipeAppliedEvent.php @@ -10,7 +10,7 @@ * Subscribers to this event should avoid modifying config or content, because * it is very likely that the recipe was applied as part of a chain of recipes, * so config and content are probably about to change again. This event is best - * used for tasks like clearing caches or updating a value in state. + * used for tasks like notifications, logging or updating a value in state. */ final class RecipeAppliedEvent extends Event {
Fixed on commit. Really hope no-one uses this for cache management.
-
alexpott β
committed 72926a56 on 10.3.x
Issue #3441308 by phenaproxima: Dispatch an event when a recipe is...
-
alexpott β
committed 72926a56 on 10.3.x
-
alexpott β
committed 19dd1f33 on 11.x
Issue #3441308 by phenaproxima: Dispatch an event when a recipe is...
-
alexpott β
committed 19dd1f33 on 11.x
- π¬π§United Kingdom alexpott πͺπΊπ
Cherry-picked to the core MR too.
Automatically closed - issue fixed for 2 weeks with no activity.