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 CreateAliveMessagesTable 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_messages', function (Blueprint $table) {
$table->increments('id');
// From field
$table->unsignedInteger('from')
->nullable()
->index();
$table->foreign('from')
->references('id')
->on('users')
->onDelete('cascade')
->onUpdate('cascade');
// To field
$table->unsignedInteger('to')
$table->foreign('to')
$table->string('body')
->nullable();
// to show message or not
$table->boolean('invisible')
->default(false);
// Process field
$table->unsignedInteger('process_id')
$table->foreign('process_id')
->on('alive_message_processes')
$table->timestamps();
});
}
* Reverse the migrations.
public function down()
Schema::dropIfExists('alive_messages');
Alive2212 /
LaravelMessageService
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.