If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
21
/** @scrutinizer ignore-call */
22
$router = $this->app->make(Router::class);
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 loadMigrationsFrom() does not exist on Ikechukwukalu\Dynamicmai...ilConfigServiceProvider.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
24
$this->/** @scrutinizer ignore-call */
25
loadMigrationsFrom(self::DB);
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 publishes() does not exist on Ikechukwukalu\Dynamicmai...ilConfigServiceProvider.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
26
$this->/** @scrutinizer ignore-call */
27
publishes([
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 mergeConfigFrom() does not exist on Ikechukwukalu\Dynamicmai...ilConfigServiceProvider.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
42
$this->/** @scrutinizer ignore-call */
43
mergeConfigFrom(
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.