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 CreateRolesTable 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(config('cortex.fort.tables.roles'), function (Blueprint $table) {
// Columns
$table->increments('id');
$table->string('name', 150);
$table->{$this->jsonable()}('title')->nullable();
$table->integer('level')->unsigned()->nullable();
$table->integer('scope')->nullable();
$table->auditable();
$table->timestamps();
// Indexes
$table->index(['scope']);
$table->unique(['name', 'scope'], 'roles_name_unique');
});
}
* Reverse the migrations.
public function down()
Schema::drop(config('cortex.fort.tables.roles'));
* Get jsonable column data type.
* @return string
protected function jsonable(): string
return DB::connection()->getPdo()->getAttribute(PDO::ATTR_DRIVER_NAME) === 'mysql'
&& version_compare(DB::connection()->getPdo()->getAttribute(PDO::ATTR_SERVER_VERSION), '5.7.8', 'ge')
? 'json' : 'text';
rinvex /
cortex-auth
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.