Job execute method

[CTOlet]

@zhuravljov Why dont you use Yii::$container->invoke([$job, 'execute']); instead of $job->execute($this);here? It will be very useful for resolving dependencies via DI container. Passing the queue object is useless IMO, we can set it to property of the job if needed. Or maybe there is another ways to simply resolve them?

[CTOlet]

Now we can do smth like

/** @var StorageService $storage */
$storage = Yii::createObject(StorageService::class);

inside the execute($queue) method.

@samdark @SilverFire @airani @luke- go to discussion

[zhuravljov]

That doesn't make sense. If you try to add DI param to execute method, fatal error will be raised, because method defined inside job interface.

[CTOlet]

@zhuravljov Yeap, that is exactly what I mean, the problem is on the Job interface. I have rewritten that interface before opening this issue and DI works perfectly. But currently implementation limits us.

[zhuravljov]

I dont see any problems.
You can make base class that contains separate method for injections:

abstract class BaseJob extends Object implements Job
{
    public function execute($queue)
    {
        if (method_exists($this, 'executeByDI')) {
            Yii::$container->invoke([$this, 'executeByDI']);
        } else {
            throw new InvalidCallException('Method executeByDI not exists.');
        }
    }
}

Override this method and use DI params.