It seems like $templateFileResolver can also be of type null; however, parameter $templateFileResolver of ntentan\honam\TemplateRenderer::__construct() does only seem to accept ntentan\honam\TemplateFileResolver, maybe add an additional type check?
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-type annotation
21
$this->templateRenderer = $templateRenderer ?? new TemplateRenderer($engineRegistry = new EngineRegistry(), /** @scrutinizer ignore-type */ $templateFileResolver);
Loading history...
22
if($engineRegistry) {
23
$engineRegistry->registerEngine('mustache', new MustacheEngine());
The call to ntentan\honam\engines\Mu...heEngine::__construct() has too few arguments starting with stringRenderingEngine.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
23
$engineRegistry->registerEngine('mustache', /** @scrutinizer ignore-call */ new MustacheEngine());
This check compares calls to functions or methods with their respective definitions.
If the call has less 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.
Loading history...
24
$engineRegistry->registerEngine('php.tpl', new PhpEngine());
The call to ntentan\honam\engines\PhpEngine::__construct() has too few arguments starting with templateRenderer.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
24
$engineRegistry->registerEngine('php.tpl', /** @scrutinizer ignore-call */ new PhpEngine());
This check compares calls to functions or methods with their respective definitions.
If the call has less 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.
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.
Loading history...
36
}
37
38
public function render(string $template, array $data)
ntentan /
honam
Loading history...