From 9cb33b5b84b658e25e5a40b5206af98389d69870 Mon Sep 17 00:00:00 2001 From: Coleman Watts Date: Sat, 29 Oct 2022 11:31:31 -0400 Subject: [PATCH] Afform - improve AbstractBehavior docblock --- ext/afform/core/Civi/Afform/AbstractBehavior.php | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/ext/afform/core/Civi/Afform/AbstractBehavior.php b/ext/afform/core/Civi/Afform/AbstractBehavior.php index c1f3d0a8ac..2ca00ef73c 100644 --- a/ext/afform/core/Civi/Afform/AbstractBehavior.php +++ b/ext/afform/core/Civi/Afform/AbstractBehavior.php @@ -24,13 +24,9 @@ use Civi\Core\Service\AutoService; * behaviors by selecting a mode. * * To enact its functionality, a behavior class can listen to any Civi hook or event. - * (the simplist way is by implementing `HookInterface`, - * or for finer control of the order of events, try the `EventSubscriberInterface`). + * (e.g. by using `EventSubscriberInterface`). * - * Notable events often used by Behaviors include `civi.afform.prefill` and `civi.afform.submit`. - * - * Note: Behavior classes can be in any namespace, but if you want the convenience of the - * `afform-behavior-php` autoloader, they must be in `\Civi\Afform\Behavior`. + * Notable events used by Behaviors include `civi.afform.validate`, `civi.afform.prefill` and `civi.afform.submit`. */ abstract class AbstractBehavior extends AutoService implements BehaviorInterface { -- 2.25.1