The PatternUpdateEvent system was added in previous releases, but writing event subscribers for this event has limited guidance. Making this more intuitive and lightweight to write will ease the process of utilizing this system. The system also fails if a subscriber is run and results in content assignment that is invalid for the latest schema, even if later subscribers would correct this. Adding a way to support this will allow for subscribers to be more easily separable for smaller areas of concern.
PatternUpdateEvent to extendPatternUpdateEvent class to simplify data accessPatternUpdateEvent class to allow for handling invalid content during updatesNone
\Drupal\patternkit\Event\PatternUpdateEvent for easier value accessibility\Drupal\patternkit\Event\PatternUpdateEvent::setContent method now accepts optional second argument to allow for assignment of invalid content that should be fixed before finally saving the updated pattern\Drupal\patternkit\EventSubscriber\PatternUpdateEventSubscriberBase for easy extension by new event subscribers\Drupal\patternkit\PatternValidationTrait Trait class for use by services needing to validate pattern content\Drupal\patternkit_test\EventSubscriber\PatternUpdateSubscriberNone
Active
9.1
Module Core
Tested the new base event subscriber extending the PatternUpdateEventSubscriberBase. Was able to verify the events trigger and worked as expected.
Automatically closed - issue fixed for 2 weeks with no activity.