Deferred event handling for bulk ops#16655
Merged
brandonkelly merged 3 commits into5.7from Feb 7, 2025
Merged
Conversation
[ci skip]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces a new
craft\events\BulkOpEvent::defer()method, which can be used in place ofEvent::on()when you want to track whether an event occurs during a bulk operation, and handle it after the bulk operation is complete.The event handler is passed the same
BulkOpEventobject you’d get if you were listening tocraft\services\Elements::EVENT_AFTER_BULK_OP. (The event may have occurred on a previous request, so there’s no way to keep track of the specific event objects that were fired.)