CreateUserActivationTable::up() - Code Metrics - Inspection of "Add tests to project" - nixsolutions/laravel-api-boilerplate - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Pull Request — master (#10)

by alexfloppy

created 2017-04-07 16:00 UTC

CreateUserActivationTable::up() A

↳ Parent: CreateUserActivationTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	14
Code Lines	9

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
c	0
b	0
f	0
dl	0
loc	14
rs	9.4285
cc	1
eloc	9
nc	1
nop	0

<?php

use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class CreateUserActivationTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('user_activation', function (Blueprint $table) {

            $table->increments('id');
            $table->integer('user_id')->unsigned();
            $table->string('token')->index();
            $table->timestamp('expired');
            $table->foreign('user_id')->references('id')->on('users')->onDelete('cascade');
        });

        Schema::table('users', function($table) {
            $table->boolean('activated')->default(false);
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::dropIfExists('user_activation');

        Schema::table('users', function($table) {
            $table->dropColumn('activated');
        });
    }
}


1			<?php
2
3			use Illuminate\Support\Facades\Schema;
4			use Illuminate\Database\Schema\Blueprint;
5			use Illuminate\Database\Migrations\Migration;
6
7			class CreateUserActivationTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2017-04-07 16:08 UTC by Report Bug Copy Issue Report PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions. 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. Loading history...
8			{
9			/**
10			* Run the migrations.
11			*
12			* @return void
13			*/
14			public function up()
15			{
16			Schema::create('user_activation', function (Blueprint $table) {
			0 ignored issues – show Bug introduced 2017-04-07 16:08 UTC by Report Bug Copy Issue Report The method `create()` does not exist on `Illuminate\Support\Facades\Schema`. Did you maybe mean `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. Loading history...
17			$table->increments('id');
18			$table->integer('user_id')->unsigned();
19			$table->string('token')->index();
20			$table->timestamp('expired');
21			$table->foreign('user_id')->references('id')->on('users')->onDelete('cascade');
22			});
23
24			Schema::table('users', function($table) {
25			$table->boolean('activated')->default(false);
26			});
27			}
28
29			/**
30			* Reverse the migrations.
31			*
32			* @return void
33			*/
34			public function down()
35			{
36			Schema::dropIfExists('user_activation');
37
38			Schema::table('users', function($table) {
39			$table->dropColumn('activated');
40			});
41			}
42			}
43

nixsolutions / laravel-api-boilerplate

Pull Request — master (#10)

CreateUserActivationTable::up() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like