Replaces __call with static methods

[shaoshiva]

Hi,

I don't see any reason to implement the search and suggest methods in __call instead of just exposing static methods ? Maybe I missed something ?

The problem of overloading the __call method from a trait is that other traits may overload it too, and it can't simply be solved by aliasing them because they all call parent::__ call, the only solution would be to manually merge the code of all the __call into a single method, but that's weird.

For example, I encountered this problem while using the Searchable trait in combination with this one :
https://github.com/Laravel-Backpack/CRUD/blob/master/src/ModelTraits/SpatieTranslatable/HasTranslations.php

[sleimanx2]

We won't be able to do the following.

$song = new Song();
$song->search()->...;

[shaoshiva]

Oops sorry for the mess with the 2 last commits...

[jfadich]

Why would you realistically want to call search on a model instance? If you already have a model, then you wouldn't be searching.