如何重写Dispatch.php中的方法

Question

I'm hard coding the $connection and $queue in over 10 files so I'm trying to clean that up. My first thought is to create some helpers that I can access in all of these files. However, I don't need those methods/variable available throughout my entire app. Instead, it would make most sense to place them in the ShouldQueue class. Any thoughts on the proper way to do this?

namespace App\Listeners\User;

use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
use Log;

class CreateJenzUser implements ShouldQueue
{

 use InteractsWithQueue;

 public $connection = 'sqs_high';

 public $queue = 'portal_high.fifo';

 //Would rather use
 public $connection = $highConnection;

 public function handle(UserBeingCreated $event)
 {
 }
}

EDIT

It turns out Laravel is creating a new instance of CreateJenzUser without the constructor.

vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php - line 479

/**
 * Create the listener and job for a queued listener.
 *
 * @param  string  $class
 * @param  string  $method
 * @param  array  $arguments
 * @return array
 */
protected function createListenerAndJob($class, $method, $arguments)
{
    $listener = (new ReflectionClass($class))->newInstanceWithoutConstructor();

    return [$listener, $this->propagateListenerOptions(
        $listener, new CallQueuedListener($class, $method, $arguments)
    )];
}

Just need to figure out how to override this method.

Answer 1

I would make a parent abstract class and extend it from all the classes that needs to use the queue. You can specify all the method that you must implement as abstract methods in the parent class so you do not need to implement the ShouldQueue interface.

So, the parent class will look like

abstract class Queue
{
     use InteractsWithQueue;

     protected $connection = 'sqs_high';

     protected $queue = 'portal_high.fifo';

     // list here all the methods in your ShouldQueue interface
     abstract protected function handle(UserBeingCreated $event);
}

Then the child class:

class CreateJenzUser extends Queue
{

    protected function handle(UserBeingCreated $event)
    {
        // your code here
    }
}

Update

If you need to keep the interface (for type hint check for example) you can extend and implement in the same time. So, the child class in this case will look like:

class CreateJenzUser extends Queue implements ShouldQueue
{

    protected function handle(UserBeingCreated $event)
    {
        // your code here
    }
}

The Queue class may not need to be abstract in this case. However, that depends on how you want to design. If you have some methods that you want to call from the parent but define in the child you can still keep it as an abstract class.

Answer 2

It sounds like that all those classes share code, that should be refactored. Probably the best option would be to extract class and then pass it as a dependency in the constructors of classes, which need that behavior.

You should also consider the fact, that trait is basically interpretator assisted copy-paste. You are just using a language structure to hide that code duplication.

PS
Don't use extends to fix this. The "extends" keyword should be read as "is a special subtype of". And user is not a special type of queue ... frankly, some could see it as an insult.