Ianrizky\Illuminate\Database\Concerns\UseCustomQueryBuilder

Complexity

Total Complexity

3

Size/Duplication

Total Lines	28
Duplicated Lines	0 %

Test Coverage

Coverage

0%

Importance

Changes	1
Bugs	0	Features	0

1 Method

Rating	Name	Duplication	Size	Complexity
A	query()	0	19	3

<?php

namespace Ianrizky\Illuminate\Database\Concerns;

use Illuminate\Database\Query\Builder;
use Illuminate\Support\Facades\Config;
use InvalidArgumentException;

trait UseCustomQueryBuilder
{
    /**
     * Get a new query builder instance.
     *
     * @return \Illuminate\Database\Query\Builder
     *
     * @throws \InvalidArgumentException
     */
    public function query(): Builder
    {
        $customQueryBuilderClass = Config::get('database.custom_query_builder_class');

        if (is_null($customQueryBuilderClass)) {
            return new Builder(
                $this, $this->getQueryGrammar(), $this->getPostProcessor()

It seems like getPostProcessor() must be provided by classes using this trait. How about adding it as abstract method to this trait?

$this of type Ianrizky\Illuminate\Database\Concerns\UseCustomQueryBuilder is incompatible with the type Illuminate\Database\ConnectionInterface expected by parameter $connection of Illuminate\Database\Query\Builder::__construct().

It seems like getQueryGrammar() must be provided by classes using this trait. How about adding it as abstract method to this trait?

            );
        }

        if (is_subclass_of($customQueryBuilderClass, Builder::class)) {
            return new $customQueryBuilderClass(
                $this, $this->getQueryGrammar(), $this->getPostProcessor()
            );
        }

        throw new InvalidArgumentException(sprintf(
            "The custom query builder class of %s must extend the base %s laravel class",
            $customQueryBuilderClass, Builder::class
        ));
    }
}