The Dispatcher class does not use the container to resolve the PendingBatch and PendingChain instances

[sebestenyb]

Laravel Version

12

PHP Version

8.3

Database Driver & Version

MySQL 8

Description

The Illuminate\Bus\Dispatcher class initiate the PendingBatch and PendingChain instances directly, instead of using the container to resolve them.

This makes impossible to extend and swap these classes.

Practical example:

• Having a multi-tenanted application, where each tenant has it's own queue (to mitigate noisy neighbour problem).
• It is possible to define a dynamic, tenant-aware queue for individual jobs, it is not easily possible to do for batches and chains.
• The developer has to specify the ->onQueue() modifier for every instance of batches and chains, which can be unnecessarily verbose.
• If the framework would let the developer to re-bind the PendingBatch and/or PendingChain instances, the dynamic queue resolution could be easily done in one place - inside the tenant aware
  descendant class.

Steps To Reproduce

Any fresh Laravel instance

[macropay-solutions]

    public function register()
    {
        $this->app->singleton(Dispatcher::class, function ($app) {
            return new Dispatcher($app, function ($connection = null) use ($app) {
                return $app[QueueFactoryContract::class]->connection($connection);
            });
        });

if you can replace \Illuminate\Bus\BusServiceProvider and register a child class for Dispatcher you can overwrite in that child the methods you are trying to change in your PR.