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 CreateTagTagsTable 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('tag__tags', 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->engine = 'InnoDB';
$table->increments('id');
$table->string('namespace');
$table->timestamps();
});
Schema::create('tag__tagged', function (Blueprint $table) {
$table->string('taggable_type');
$table->integer('taggable_id')->unsigned();
$table->integer('tag_id')->unsigned();
$table->index(['taggable_type', 'taggable_id']);
}
* Reverse the migrations.
public function down()
Schema::drop('tag__tags');
Schema::drop('tag__tagged');
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.