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;
class CreateEventStore 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()
if (!Schema::hasTable('event_store')) {
Schema::create('event_store', function (Blueprint $table) {
$table->increments('id');
$table->string('identifier', 40);
$table->unsignedInteger('sequence');
$table->string('event', 100);
$table->text('payload');
$table->timestamps();
$table->unique(['identifier', 'sequence'], 'entity_version');
$table->index('identifier');
});
}
* Reverse the migrations.
public function down()
// Event Store should never be deleted.
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.