for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
declare(strict_types=1);
use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
class CreateAbilitiesTable 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('rinvex.fort.tables.abilities'), function (Blueprint $table) {
// Columns
$table->increments('id');
$table->string('action');
$table->string('resource');
$table->string('policy')->nullable();
$table->{$this->jsonable()}('name');
$table->{$this->jsonable()}('description')->nullable();
$table->timestamps();
$table->softDeletes();
// Indexes
$table->unique(['action', 'resource']);
});
}
* Reverse the migrations.
public function down()
Schema::dropIfExists(config('rinvex.fort.tables.abilities'));
* Get jsonable column data type.
* @return string
protected function jsonable()
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 /
laravel-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.