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 CreateAliveMessageEventsTable 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('alive_message_events', function (Blueprint $table) {
$table->increments('id');
$table->text('model');
$table->enum('type', [
'Saving', 'Creating', 'Updating', 'Deleting', 'Restoring',
'Saved', 'Created', 'Updated', 'Deleted', 'Restored',
'pivotAttaching', 'pivotDetaching', 'pivotUpdating',
'pivotAttached', 'pivotDetached', 'pivotUpdated',
]);
$table->text('rules');
$table->timestamps();
});
}
* Reverse the migrations.
public function down()
Schema::dropIfExists('alive_message_events');
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.