for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
use Illuminate\Support\Facades\Schema;
class CreateMembersTable 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(
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.
'members',
function (Blueprint $table) {
$table->increments('id');
$table->string('email');
$table->string('password', 65);
$table->string('first_name');
$table->string('last_name');
$table->string('faculty');
$table->string('field_of_study');
$table->integer('year_of_graduation');
$table->string('photo')->nullable();
$table->date('birthday');
$table->string('facebook')->nullable();
$table->string('twitter')->nullable();
$table->string('google_plus')->nullable();
$table->string('phone')->nullable();
$table->string('website')->nullable();
$table->boolean('board_member')->default(false);
$table->string('position_title')->nullable();
$table->boolean('approved')->default(false);
$table->boolean('alumni')->default(false);
$table->string('remember_token')->nullable();
$table->timestamps();
$table->unique('email');
}
);
* Reverse the migrations.
public function down()
Schema::drop('members');
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.