for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
class CreatePreferencesTable 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('preferences', function (Blueprint $table) {
$table->increments('id');
$table->string('key');
$table->string('value');
$table->enum('type', ['string', 'bool', 'int', 'float', 'array', 'time', 'json'])->default('string');
$table->string('preferenceable_type');
$table->integer('preferenceable_id')->unsigned();
$table->nullableTimestamps();
$table->unique(['key', 'preferenceable_type', 'preferenceable_id']);
});
}
* Reverse the migrations.
public function down()
Schema::drop('preferences');
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.