CreateUsersActivationTable::up() - Code Metrics - Inspection of "Merge pull request #32 from AudithSoftworks/auth" - AudithSoftworks/Basis - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( b1c4b6...a05019 )

by Şəhriyar

created 2016-04-18 12:50 UTC

CreateUsersActivationTable::up() A

↳ Parent: CreateUsersActivationTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	14
Code Lines	10

Duplication

Lines	0
Ratio	0 %

Importance

Changes	1
Bugs	1	Features	1

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

<?php

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

class CreateUsersActivationTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('users_activations', function (Blueprint $table) {
            $table->engine = 'InnoDB';
            $table->increments('id');
            $table->unsignedInteger('user_id');
            $table->string('code');
            $table->boolean('completed')->default(0);
            $table->timestamp('completed_at')->nullable();
            $table->timestamps();

            $table->foreign('user_id')->references('id')->on('users')->onUpdate('cascade')->onDelete('cascade');
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::drop('users_activations');
    }
}


1			<?php
2
3			use Illuminate\Database\Schema\Blueprint;
4			use Illuminate\Database\Migrations\Migration;
5
6			class CreateUsersActivationTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2016-04-18 12:04 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...
7			{
8			/**
9			* Run the migrations.
10			*
11			* @return void
12			*/
13			public function up()
14			{
15			Schema::create('users_activations', function (Blueprint $table) {
16			$table->engine = 'InnoDB';
17			$table->increments('id');
18			$table->unsignedInteger('user_id');
19			$table->string('code');
20			$table->boolean('completed')->default(0);
21			$table->timestamp('completed_at')->nullable();
22			$table->timestamps();
23
24			$table->foreign('user_id')->references('id')->on('users')->onUpdate('cascade')->onDelete('cascade');
25			});
26			}
27
28			/**
29			* Reverse the migrations.
30			*
31			* @return void
32			*/
33			public function down()
34			{
35			Schema::drop('users_activations');
36			}
37			}
38

AudithSoftworks / Basis

Push — master ( b1c4b6...a05019 )

CreateUsersActivationTable::up() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like