for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;
class CreateChangesTable 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('loggable_changes', 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->unsignedInteger('user_id');
$table->unsignedInteger('model_id');
$table->string('model_type');
$table->enum('type', ['create', 'update', 'delete', 'restore'])->default('update');
$table->string('set', 32)->nullable();
$table->string('attribute')->nullable();
$table->text('old_value')->nullable();
$table->text('new_value')->nullable();
$table->timestamps();
$table->index('user_id');
$table->index('model_id');
$table->index('type');
$table->index('set');
});
}
* Reverse the migrations.
public function down()
Schema::dropTable('loggable_changes');
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.