If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
6
$logfile->/** @scrutinizer ignore-call */
7
setPath(__DIR__);
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.
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
7
$logfile->/** @scrutinizer ignore-call */
8
setUser(['id' => '4']);
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.
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
8
$logfile->/** @scrutinizer ignore-call */
9
setTags([
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.
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.
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.