Should the return type not be null|\Symfony\Component\...|string|array|\stdClass? Also, consider making the array more specific, something like array<String>, or String[].
This check compares the return type specified in the @return annotation of a function
or method doc comment with the types returned by the function and raises an issue if they
mismatch.
If the return type contains the type array, this check recommends the use of
a more specific type like String[] or array<String>.
The return type of return \Symfony\Componen...se($this->get(), true); (null|Symfony\Component\Y...e|string|array|stdClass) is incompatible with the return type declared by the interface NeedleProject\FileIo\Con...tentInterface::getArray of type array.
If you return a value from a function or method, it should be a sub-type of the
type that is given by the parent type f.e. an interface, or abstract method.
This is more formally defined by the
Lizkov substitution principle,
and guarantees that classes that depend on the parent type can use any instance
of a child type interchangably. This principle also belongs to the
SOLID principles
for object oriented design.
Our function my_function expects a Post object, and outputs the author
of the post. The base class Post returns a simple string and outputting a
simple string will work just fine. However, the child class BlogPost which
is a sub-type of Post instead decided to return an object, and is
therefore violating the SOLID principles. If a BlogPost were passed to
my_function, PHP would not complain, but ultimately fail when executing the
strtoupper call in its body.
This check compares the return type specified in the
@return
annotation of a function or method doc comment with the types returned by the function and raises an issue if they mismatch.If the return type contains the type array, this check recommends the use of a more specific type like
String[]
orarray<String>
.