for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
use Illuminate\Support\Facades\Schema;
class CreateFilesTable extends Migration
You can fix this by adding a namespace to your class:
namespace YourVendor; class YourClass { }
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.
{
/**
* Run the migrations.
*
* @return void
*/
public function up()
Schema::create('files', function (Blueprint $table) {
create()
Illuminate\Support\Facades\Schema
createFreshMockInstance()
This check marks calls to methods that do not seem to exist on an object.
This is most likely the result of a method being renamed without all references to it being renamed likewise.
$table->increments('id');
$table->string('file_id')->unique();
$table->string('name');
$table->string('extension')->nullable();
$table->string('path')->nullable();
$table->string('mime_type');
$table->integer('byte_size');
$table->json('data');
$table->string('disk');
$table->dateTime('saved_at');
});
}
* Reverse the migrations.
public function down()
Schema::drop('files');
You can fix this by adding a namespace to your class:
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.