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 CreateAliveMessageProcessesTable 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_processes', function (Blueprint $table) {
$table->increments('id');
$table->enum('type', ['Sms', 'Notification', 'Social','Email'])
->nullable();
$table->unsignedInteger('scope')
$table->text('from')
$table->text('to')
$table->text('body');
// to show message or not
$table->boolean('invisible')
->dafault(false);
$table->text('launch_time'); // it can a field of model if string and if data time
// Event field
$table->unsignedInteger('event_id')
->index();
$table->foreign('event_id')
->references('id')
->on('alive_message_events')
->onDelete('cascade')
->onUpdate('cascade');
$table->timestamps();
});
}
* Reverse the migrations.
public function down()
Schema::dropIfExists('alive_message_processes');
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.