[5.x] Allow any queued class to be silenced #1241
Merged
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.
This PR looks bigger than it is due to moving a chunk of Fixtures and Unit tests into the Feature directory.
What problem does this solve?
This allows any queued class to be silenced - we have a lot of listeners that fire constantly and most of them are trivial so we don't need to see them in the completed list.
Related: #1239
This PR will allow any queued class to be silenced - the initial implementation meant only queued Jobs could be silenced. Now, any Mailable, Notification, Listener, Broadcast or Job can be silenced by implementing the
Silenced
interface.The main changes to this PR are;
config
helper is useable inJobPayload
Silenced
interfaceMarkJobAsComplete
into the payloadI wasn't 100% sure on the silenced mailable test but did it the only way I could think to make it easy by adding the mock to the Horizon silenced config