[1.x] [extensibility] feat: allow classes that extends AbstractJob
to be placed on a specified queue
#4026
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.
Changes proposed in this pull request:
Add a static property to
AbstractJob
, so that any class extending it may specify which queue it should be dispatched on.Reviewers should focus on:
All jobs within core and extensions have had their constructor updated to also call
parent::__construct()
. My understanding that if a 3rd party does not call the parent constructor, it simply means that the$onQueue
won't be set, therefore not breaking any compatibility?QA
Necessity
Confirmed
composer test
).Required changes: