Bugfix | Fix the webhook connection and queues.

[Kyon147]

Issue:

At the moment we return null if connection and queue are not set in the config which by default that is how it is.

This means that we always force webhooks onto the default queue so that using onQueue or onConnectionare always null from the dispatch.

[Kyon147]

@enmaboya @rvibit can you please review my code if you have time. No worries if not, but I'd rather not self approve my own code.

[rvibit]

@enmaboya @rvibit can you please review my code if you have time. No worries if not, but I'd rather not self approve my own code.

looks fine to me, it'll use default connection and queue when not provided explicitly correct?

[Kyon147]

@rvibit yeah - the issue with null, is that it is causing everything to end up on the default queue, which means that you can't set a queue inside a job for example or of the back of another job.

As the main handler is always taking precedence, so omitting the method when not needed, means it just allows for it to be overwritten downstream as expected.

If left blank, then it will just fallback to the default queue as you mentioned.