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 CreateSessionsTable 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('session.table'), function (Blueprint $table) {
create()
Illuminate\Support\Facades\Schema
createFreshMockInstance()
This check marks calls to methods that do not seem to exist on an object.
This is most likely the result of a method being renamed without all references to it being renamed likewise.
// Columns
$table->string('id');
$table->integer('user_id')->unsigned()->nullable();
$table->string('ip_address', 45)->nullable();
$table->text('user_agent')->nullable();
$table->text('payload');
$table->integer('last_activity');
// Indexes
$table->unique('id');
$table->foreign('user_id')->references('id')->on(config('rinvex.fort.tables.users'))
->onDelete('cascade')->onUpdate('cascade');
});
}
* Reverse the migrations.
public function down()
Schema::dropIfExists(config('session.table'));
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.