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 CreateHistoriesTable 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('histories', function (Blueprint $table) {
$table->increments('id');
$table->uuid('uuid')->unique();
$table->string('content_type');
$table->integer('content_id');
$table->integer('workflow_id')->unsigned()->nullable();
$table->integer('workflow_transition_id')->unsigned()->nullable();
$table->integer('from_state');
$table->integer('to_state');
$table->integer('user_id');
$table->text('message');
$table->softDeletes();
$table->timestamps();
});
}
* Reverse the migrations.
public function down()
Schema::dropIfExists('histories');
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.