Trait method newEloquentBuilder has not been applied, because there are collisions with other trait methods

[eelco2k]

Issue

Trait method newEloquentBuilder has not been applied, because there are collisions with other trait methods on App\Models\Flight.

I found out that i'm also using \Grimzy\LaravelMysqlSpatial Trait in this model.
and reading this issue it looks like it has to do with this package.
grimzy/laravel-mysql-spatial#17

I'm not sure if it's possible to implement a method to fix this issue in this package or that i do have to create my own custom "Illuminate\Database\Eloquent\Builder".

Environment

Laravel Version: 5.5.40
Laravel Model Caching Package Version: 0.2.62
PHP Version: PHP 7.1.8

Operating System & Version: Mac OS X

Stack Trace

(1/1) FatalErrorExceptionTrait method newEloquentBuilder has not been applied, because there are collisions with other trait methods on App\Models\Flight
--

[mikebronner]

Hi @eelco2k, off the top of my head, I believe this is something you will have to resolve locally in your app. Please let me know if you do find a solution, so I can take a look and see if it would be possible to implement in the package.

[eelco2k]

as @grimzy commented out in this issue: grimzy/laravel-mysql-spatial#17 he wrote a custom Illuminate\Database\Eloquent\Builder and extending own packages classes with a Trait.

Perhaps this would be a good method to do as well for laravel-model-caching.

[eelco2k]

i've tried to move the functions in CachedBuilder.php into a Trait but this didn't work sadly.

I've also tried this in conjuction with the dev-builder-as-trait branch of the grimzy/laravel-mysql-spatial but i'm still getting the same errors.

So no solution yet.

[mikebronner]

Yea, I don't think there is an easy solution for this at this time. I'm closing this for now. Please re-open if you have further information that may help out. Thanks for looking into it!

[Spodnet]

I had this problem with \Kalnoy\Nestedset\NodeTrait

I think this is working as a simple solution in my case, the node trait ran

public function newEloquentBuilder($query) {
    return new QueryBuilder($query);
}

Looking at the code in the model caching, it was ok to simply override in my model

use \GeneaLabs\LaravelModelCaching\Traits\Cachable {
        \GeneaLabs\LaravelModelCaching\Traits\Cachable::newEloquentBuilder insteadof \Kalnoy\Nestedset\NodeTrait;
}

I would imagine providing the trait that's causing issues doesn't do anything that would cause issues overriding might solve it. Otherwise you'll need to write your own trait to handle the conflict cases I would think.

I'm still testing for any side effects...

[Daniyal-Javani]

I had this problem with \Kalnoy\Nestedset\NodeTrait

I think this is working as a simple solution in my case, the node trait ran

public function newEloquentBuilder($query) {
    return new QueryBuilder($query);
}

Looking at the code in the model caching, it was ok to simply override in my model

use \GeneaLabs\LaravelModelCaching\Traits\Cachable {
        \GeneaLabs\LaravelModelCaching\Traits\Cachable::newEloquentBuilder insteadof \Kalnoy\Nestedset\NodeTrait;
}

I would imagine providing the trait that's causing issues doesn't do anything that would cause issues overriding might solve it. Otherwise you'll need to write your own trait to handle the conflict cases I would think.

I'm still testing for any side effects...

@Spodnet Have you found any side effects?

[Spodnet]

No issues so far :)

[indowebdeveloper]

I've tried @Spodnet solution above, and found that you will be no longer able to use any of \Kalnoy\Nestedset\NodeTrait method, for example, withDepth will no longer be able to use...