The call to Epesi\Core\Data\HasEpesiConnection::__construct() has too many arguments starting with $atkDb.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
18
return /** @scrutinizer ignore-call */ new static($atkDb, $defaults);
This check compares calls to functions or methods with their respective definitions.
If the call has more arguments than are defined, it raises an issue.
If a function is defined several times with a different number of parameters, the
check may pick up the wrong definition and report false positives. One codebase
where this has been known to happen is Wordpress. Please note the @ignore annotation hint above.
The expression return new static($atkDb, $defaults) returns the type Epesi\Core\Data\HasEpesiConnection which is incompatible with the documented return type atk4\data\Model.
It seems like addCondition() must be provided by classes using this trait. How about adding it as abstract method to this trait?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
The expression return collect(self::cre...))->pluck($value, $key) returns the type Illuminate\Support\Collection which is incompatible with the documented return type Epesi\Core\Data\HasEpesiConnection.
x-systems /
epesi-core
Loading history...
This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.
If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above.