CreateHistoriesTable::up() - Code Metrics - bantenprov/vue-workflow - Measure and Improve Code Quality continuously with Scrutinizer

CreateHistoriesTable::up() A
last analyzed 2018-05-10 08:29 UTC

↳ Parent: CreateHistoriesTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	17
Code Lines	14

Duplication

Lines	0
Ratio	0 %

Importance

Changes

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

<?php

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

class CreateHistoriesTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('histories', function (Blueprint $table) {
            $table->increments('id');
            $table->uuid('uuid')->unique();
            $table->string('content_type');
            $table->integer('content_id');
            $table->integer('workflow_id')->unsigned()->nullable();           
            $table->integer('workflow_transition_id')->unsigned()->nullable();            
            $table->integer('from_state');
            $table->integer('to_state');
            $table->integer('user_id');
            $table->text('message');
            $table->softDeletes();
            $table->timestamps();
        });
    }

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


1			<?php
2
3			use Illuminate\Support\Facades\Schema;
4			use Illuminate\Database\Schema\Blueprint;
5			use Illuminate\Database\Migrations\Migration;
6
7			class CreateHistoriesTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2018-04-01 17:12 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('histories', function (Blueprint $table) {
17			$table->increments('id');
18			$table->uuid('uuid')->unique();
19			$table->string('content_type');
20			$table->integer('content_id');
21			$table->integer('workflow_id')->unsigned()->nullable();
22			$table->integer('workflow_transition_id')->unsigned()->nullable();
23			$table->integer('from_state');
24			$table->integer('to_state');
25			$table->integer('user_id');
26			$table->text('message');
27			$table->softDeletes();
28			$table->timestamps();
29			});
30			}
31
32			/**
33			* Reverse the migrations.
34			*
35			* @return void
36			*/
37			public function down()
38			{
39			Schema::dropIfExists('histories');
40			}
41			}
42

bantenprov / vue-workflow

CreateHistoriesTable::up() A last analyzed 2018-05-10 08:29 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

CreateHistoriesTable::up() A
last analyzed 2018-05-10 08:29 UTC