for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
namespace Imanghafoori\LaravelMicroscope\Commands;
use Illuminate\Console\Command;
use Imanghafoori\LaravelMicroscope\Analyzers\ComposerJson;
use Imanghafoori\LaravelMicroscope\ErrorReporters\ErrorPrinter;
use Imanghafoori\LaravelMicroscope\GenerateCode;
use Imanghafoori\LaravelMicroscope\LaravelPaths\FilePath;
class CheckExpansions extends Command
{
protected $signature = 'check:generate';
protected $description = 'Generates code';
public function handle(ErrorPrinter $errorPrinter)
$this->info('Scanning for Empty Provider Files');
$errorPrinter->printer = $this->output;
$autoload = ComposerJson::readAutoload();
foreach ($autoload as $psr4Namespace => $psr4Path) {
$files = FilePath::getAllPhpFiles($psr4Path);
GenerateCode::serviceProvider($files, $psr4Path, $psr4Namespace, $this);
$files
object<Symfony\Component\Finder\Finder>
object<Imanghafoori\LaravelMicroscope\iterable>
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example:
function acceptsInteger($int) { } $x = '123'; // string "123" // Instead of acceptsInteger($x); // we recommend to use acceptsInteger((integer) $x);
}
imanghafoori1 /
laravel-microscope
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example: