Update Loader to support Task Handlers#6
Merged
Conversation
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.
Context
This PR adds support for the new
phpnomad/taskssystem by updating theCanLoadInitializerstrait to recognize and process initializers that implementHasTaskHandlers.The new task system introduced in
phpnomad/tasks v2.0.0aligns closely with PHPNomad’s event architecture, allowing developers to define tasks as value objects and register one or more handlers to be executed in sequence. Like events, tasks are registered declaratively via initializers, and their dispatch logic is delegated to a platform-specificTaskStrategy.What Changed
HasTaskHandlers.TaskStrategyinstance viaattach().HasListenersis handled for events and supports multiple handlers per task class.Why This Matters
The addition ensures that the task system fully integrates with the PHPNomad bootstrap lifecycle and adheres to the same modular, initializer-driven design used throughout the framework.
By delegating handler registration to the loader:
This update is necessary for any system adopting the new task architecture and completes the foundational work needed to support task execution across platforms like WordPress, Redis, or CLI.