for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
class CreateTracksTable 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('tracks', 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('driver');
$table->string('queue_id');
$table->text('payload');
$table->integer('attempts');
$table->string('job_name');
$table->text('meta')->nullable();
$table->timestamp('queue_at')->nullable();
$table->timestamp('process_at')->nullable();
$table->timestamp('succeed_at')->nullable();
$table->timestamp('failed_at')->nullable();
});
}
* Reverse the migrations.
public function down()
Schema::drop('tracks');
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.