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;
use Illuminate\Support\Facades\Schema;
class CreateFightersGroupTable 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('fighters_groups', 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.
$table->increments('id');
$table->integer('championship_id')->unsigned()->index();
$table->tinyInteger('area');
$table->tinyInteger('order');
$table->timestamps();
$table->engine = 'InnoDB';
$table->foreign('championship_id')
->references('id')
->onUpdate('cascade')
->on('championship')
->onDelete('cascade');
});
}
* Reverse the migrations.
public function down()
DB::statement('SET FOREIGN_KEY_CHECKS = 0');
Schema::dropIfExists('fighters_groups');
DB::statement('SET FOREIGN_KEY_CHECKS = 1');
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.