CreatePreferencesTable::up() - Code Metrics - Inspection of "Update laravel-auto-presenter dependency" - timegridio/concierge - Measure and Improve Code Quality continuously with Scrutinizer

Test Failed

Pull Request — master (#3)

unknown

created 2018-07-14 10:16 UTC

CreatePreferencesTable::up() A

↳ Parent: CreatePreferencesTable

Complexity

Conditions	1
Paths	1

Size

Total Lines

Duplication

Lines	0
Ratio	0 %

Code Coverage

Tests	11
CRAP Score	1

Importance

Changes

Metric	Value
dl	0
loc	14
ccs	11
cts	11
cp	1
rs	9.7998
c	0
b	0
f	0
cc	1
nc	1
nop	0
crap	1

<?php

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

class CreatePreferencesTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('preferences', function (Blueprint $table) {
            $table->increments('id');
            $table->string('key');
            $table->string('value');
            $table->enum('type', ['string', 'bool', 'int', 'float', 'array', 'time', 'json'])->default('string');
            $table->string('preferenceable_type');
            $table->integer('preferenceable_id')->unsigned();
            $table->nullableTimestamps();

            $table->unique(['key', 'preferenceable_type', 'preferenceable_id']);
        });
    }

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


1		<?php
2
3		use Illuminate\Database\Migrations\Migration;
4		use Illuminate\Database\Schema\Blueprint;
5
6		class CreatePreferencesTable extends Migration
		0 ignored issues – show Coding Style Compatibility introduced 2016-02-03 04:24 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	152	Schema::create('preferences', function (Blueprint $table) {
16	152	$table->increments('id');
17	152	$table->string('key');
18	152	$table->string('value');
19	152	$table->enum('type', ['string', 'bool', 'int', 'float', 'array', 'time', 'json'])->default('string');
20	152	$table->string('preferenceable_type');
21	152	$table->integer('preferenceable_id')->unsigned();
22	152	$table->nullableTimestamps();
23
24	152	$table->unique(['key', 'preferenceable_type', 'preferenceable_id']);
25	152	});
26	152	}
27
28		/**
29		* Reverse the migrations.
30		*
31		* @return void
32		*/
33		public function down()
34		{
35		Schema::drop('preferences');
36		}
37		}
38

timegridio / concierge

Pull Request — master (#3)

CreatePreferencesTable::up() A

Complexity

Size

Duplication

Code Coverage

Importance

Duplication Side-by-Side

Filter issues like