Skip to content

Allow unique and non-unique together #6

@royduin

Description

@royduin

In the Horizon config I've:

'queue' => ['default', 'low'],
'balance' => false,

So first everything in the default queue will be handled. When it's empty the low queue will be processed. Now I only like to "uniquely" queued listeners on the low queue. That's currently not possible because "uniquely" works with a custom connection. It would be awesome to have a job/listener implement an interface (I think that's better in this case in comparison with a trait currently used) and depending on that it will be "uniquelied".

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions