The method isEmpty() does not seem to exist on object<Spatie\CollectionMacros\Macros\Transpose>.
This check looks for calls to methods that do not seem to exist on a given type.
It looks for the method on the type itself as well as in inherited classes or
implemented interfaces.
This is most likely a typographical error or the method has been renamed.
The method first() does not seem to exist on object<Spatie\CollectionMacros\Macros\Transpose>.
This check looks for calls to methods that do not seem to exist on a given type.
It looks for the method on the type itself as well as in inherited classes or
implemented interfaces.
This is most likely a typographical error or the method has been renamed.
The class Spatie\CollectionMacros\Macros\Countable does not exist. Did you forget a USE statement, or did you not list all dependencies?
This error could be the result of:
1. Missing dependencies
PHP Analyzer uses your composer.json file (if available) to determine the
dependencies of your project and to determine all the available classes and functions.
It expects the composer.json to be in the root folder of your repository.
Are you sure this class is defined by one of your dependencies, or did you maybe
not list a dependency in either the require or require-dev section?
2. Missing use statement
PHP does not complain about undefined classes in ìnstanceof checks. For
example, the following PHP code will work perfectly fine:
if($xinstanceofDoesNotExist){// Do something.}
If you have not tested against this specific condition, such errors might go
unnoticed.
Loading history...
28
29
array_walk($this->items, function ($row) use ($expectedLength) {
The class Spatie\CollectionMacros\Macros\Countable does not exist. Did you forget a USE statement, or did you not list all dependencies?
This error could be the result of:
1. Missing dependencies
PHP Analyzer uses your composer.json file (if available) to determine the
dependencies of your project and to determine all the available classes and functions.
It expects the composer.json to be in the root folder of your repository.
Are you sure this class is defined by one of your dependencies, or did you maybe
not list a dependency in either the require or require-dev section?
2. Missing use statement
PHP does not complain about undefined classes in ìnstanceof checks. For
example, the following PHP code will work perfectly fine:
if($xinstanceofDoesNotExist){// Do something.}
If you have not tested against this specific condition, such errors might go
unnoticed.
Loading history...
31
throw new \LengthException("Element's length must be equal.");
The call to Transpose::__construct() has too many arguments starting with $items.
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.
In this case you can add the @ignorePhpDoc
annotation to the duplicate definition and it will be ignored.
The method getArrayableItems() does not seem to exist on object<Spatie\CollectionMacros\Macros\Transpose>.
This check looks for calls to methods that do not seem to exist on a given type.
It looks for the method on the type itself as well as in inherited classes or
implemented interfaces.
This is most likely a typographical error or the method has been renamed.
The call to Transpose::__construct() has too many arguments starting with $items.
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.
In this case you can add the @ignorePhpDoc
annotation to the duplicate definition and it will be ignored.
This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces.
This is most likely a typographical error or the method has been renamed.